pg_ctl kill 的几种方式

最新推荐文章于 2024-07-26 11:05:00 发布
最新推荐文章于 2024-07-26 11:05:00 发布
阅读量1.6k 收藏 1
点赞数
分类专栏： # postgresql setup upgrade 文章标签： pg_ctl kill
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/ctypyb2002/article/details/84651500
版权

pg_ctl kill

$ pg_ctl --help
Usage:
  pg_ctl kill    SIGNALNAME PID

Allowed signal names for kill:
  ABRT HUP INT QUIT TERM USR1 USR2

pg_ctl kill TERM

# /etc/init.d/postgresql restart
# ps -ef|grep -i post|grep -v grep
postgres  8454     1  0 14:13 ?        00:00:00 /usr/lib/postgresql/9.6/bin/postgres -D /data/pg9.6/main -c config_file=/etc/postgresql/9.6/main/postgresql.conf
postgres  8455  8454  0 14:13 ?        00:00:00 postgres: 9.6/main: logger process   
postgres  8457  8454  0 14:13 ?        00:00:00 postgres: 9.6/main: checkpointer process   
postgres  8458  8454  0 14:13 ?        00:00:00 postgres: 9.6/main: writer process   
postgres  8459  8454  0 14:13 ?        00:00:00 postgres: 9.6/main: wal writer process   
postgres  8460  8454  0 14:13 ?        00:00:00 postgres: 9.6/main: autovacuum launcher process   
postgres  8461  8454  0 14:13 ?        00:00:00 postgres: 9.6/main: archiver process   
postgres  8462  8454  0 14:13 ?        00:00:00 postgres: 9.6/main: stats collector process   
postgres  8490  8454  0 14:13 ?        00:00:00 postgres: 9.6/main: wal sender process repl 192.168.56.92(34380) streaming 0/1E0000D0
postgres  8502  7488  0 14:15 pts/0    00:00:00 /usr/lib/postgresql/9.6/bin/psql
postgres  8510  8454  0 14:15 ?        00:00:00 postgres: 9.6/main: postgres postgres [local] idle


$ pg_ctl kill TERM 8454


2018-11-30 14:16:03.798 CST,,,8454,,5c00d516.2106,3,,2018-11-30 14:13:42 CST,,0,LOG,00000,"received smart shutdown request",,,,,,,,,""
2018-11-30 14:16:03.798 CST,,,8460,,5c00d516.210c,2,,2018-11-30 14:13:42 CST,1/0,0,LOG,00000,"autovacuum launcher shutting down",,,,,,,,,""

pg_ctl kill INT

# /etc/init.d/postgresql restart
# ps -ef|grep -i post|grep -v grep
postgres  8568     1  0 14:25 ?        00:00:00 /usr/lib/postgresql/9.6/bin/postgres -D /data/pg9.6/main -c config_file=/etc/postgresql/9.6/main/postgresql.conf
postgres  8569  8568  0 14:25 ?        00:00:00 postgres: 9.6/main: logger process   
postgres  8571  8568  0 14:25 ?        00:00:00 postgres: 9.6/main: checkpointer process   
postgres  8572  8568  0 14:25 ?        00:00:00 postgres: 9.6/main: writer process   
postgres  8573  8568  0 14:25 ?        00:00:00 postgres: 9.6/main: wal writer process   
postgres  8574  8568  0 14:25 ?        00:00:00 postgres: 9.6/main: autovacuum launcher process   
postgres  8575  8568  0 14:25 ?        00:00:00 postgres: 9.6/main: archiver process   
postgres  8576  8568  0 14:25 ?        00:00:00 postgres: 9.6/main: stats collector process   
postgres  8605  8568  0 14:25 ?        00:00:00 postgres: 9.6/main: wal sender process repl 192.168.56.92(34392) streaming 0/1F0000D0
postgres  8609  7488  0 14:26 pts/0    00:00:00 /usr/lib/postgresql/9.6/bin/psql
postgres  8617  8568  0 14:26 ?        00:00:00 postgres: 9.6/main: postgres postgres [local] idle


$ pg_ctl kill INT 8568

2018-11-30 14:27:20.260 CST,,,8568,,5c00d7e5.2178,3,,2018-11-30 14:25:41 CST,,0,LOG,00000,"received fast shutdown request",,,,,,,,,""
2018-11-30 14:27:20.260 CST,,,8568,,5c00d7e5.2178,4,,2018-11-30 14:25:41 CST,,0,LOG,00000,"aborting any active transactions",,,,,,,,,""
2018-11-30 14:27:20.260 CST,"postgres","postgres",8617,"[local]",5c00d80b.21a9,3,"idle",2018-11-30 14:26:19 CST,3/0,0,FATAL,57P01,"terminating connection due to administrator command",,,,,,,,,"psql"
2018-11-30 14:27:20.260 CST,"postgres","postgres",8617,"[local]",5c00d80b.21a9,4,"idle",2018-11-30 14:26:19 CST,,0,LOG,00000,"disconnection: session time: 0:01:00.280 user=postgres database=postgres host=[local]",,,,,,,,,"psql"
2018-11-30 14:27:20.262 CST,,,8574,,5c00d7e5.217e,2,,2018-11-30 14:25:41 CST,1/0,0,LOG,00000,"autovacuum launcher shutting down",,,,,,,,,""
2018-11-30 14:27:20.269 CST,,,8571,,5c00d7e5.217b,1,,2018-11-30 14:25:41 CST,,0,LOG,00000,"shutting down",,,,,,,,,""
2018-11-30 14:27:20.678 CST,,,8571,,5c00d7e5.217b,2,,2018-11-30 14:25:41 CST,,0,LOG,00000,"checkpoint starting: shutdown immediate",,,,,,,,,""
2018-11-30 14:27:20.823 CST,,,8571,,5c00d7e5.217b,3,,2018-11-30 14:25:41 CST,,0,LOG,00000,"checkpoint complete: wrote 0 buffers (0.0%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=0.000 s, sync=0.000 s, total=0.150 s; sync files=0, longest=0.000 s, average=0.000 s; distance=16384 kB, estimate=16384 kB",,,,,,,,,""
2018-11-30 14:27:21.092 CST,"repl","",8605,"192.168.56.92:34392",5c00d7e9.219d,3,"streaming 0/20000098",2018-11-30 14:25:45 CST,,0,LOG,00000,"disconnection: session time: 0:01:35.875 user=repl database= host=192.168.56.92 port=34392",,,,,,,,,"walreceiver"
2018-11-30 14:27:21.104 CST,,,8568,,5c00d7e5.2178,5,,2018-11-30 14:25:41 CST,,0,LOG,00000,"database system is shut down",,,,,,,,,""

pg_ctl kill QUIT

# /etc/init.d/postgresql restart
# ps -ef|grep -i post|grep -v grep
postgres  8652     1  0 14:31 ?        00:00:00 /usr/lib/postgresql/9.6/bin/postgres -D /data/pg9.6/main -c config_file=/etc/postgresql/9.6/main/postgresql.conf
postgres  8653  8652  0 14:31 ?        00:00:00 postgres: 9.6/main: logger process   
postgres  8655  8652  0 14:31 ?        00:00:00 postgres: 9.6/main: checkpointer process   
postgres  8656  8652  0 14:31 ?        00:00:00 postgres: 9.6/main: writer process   
postgres  8657  8652  0 14:31 ?        00:00:00 postgres: 9.6/main: wal writer process   
postgres  8658  8652  0 14:31 ?        00:00:00 postgres: 9.6/main: autovacuum launcher process   
postgres  8659  8652  0 14:31 ?        00:00:00 postgres: 9.6/main: archiver process   
postgres  8660  8652  0 14:31 ?        00:00:00 postgres: 9.6/main: stats collector process   
postgres  8668  8652  0 14:31 ?        00:00:00 postgres: 9.6/main: wal sender process repl 192.168.56.92(34504) streaming 0/200000D0
postgres  8693  7488  1 14:32 pts/0    00:00:00 /usr/lib/postgresql/9.6/bin/psql
postgres  8701  8652  0 14:32 ?        00:00:00 postgres: 9.6/main: postgres postgres [local] idle

$ pg_ctl kill QUIT 8652

2018-11-30 14:33:24.257 CST,,,8652,,5c00d95a.21cc,3,,2018-11-30 14:31:54 CST,,0,LOG,00000,"received immediate shutdown request",,,,,,,,,""
2018-11-30 14:33:24.257 CST,"postgres","postgres",8701,"[local]",5c00d99a.21fd,3,"idle",2018-11-30 14:32:58 CST,3/0,0,WARNING,57P02,"terminating connection because of crash of another server process","The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.","In a moment you should be able to reconnect to the database and repeat your command.",,,,,,,"psql"
2018-11-30 14:33:24.258 CST,"repl","",8668,"192.168.56.92:34504",5c00d95c.21dc,3,"streaming 0/200000D0",2018-11-30 14:31:56 CST,2/0,0,WARNING,57P02,"terminating connection because of crash of another server process","The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.","In a moment you should be able to reconnect to the database and repeat your command.",,,,,,,"walreceiver"
2018-11-30 14:33:24.264 CST,,,8658,,5c00d95a.21d2,2,,2018-11-30 14:31:54 CST,1/0,0,WARNING,57P02,"terminating connection because of crash of another server process","The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.","In a moment you should be able to reconnect to the database and repeat your command.",,,,,,,""
2018-11-30 14:33:24.272 CST,,,8652,,5c00d95a.21cc,4,,2018-11-30 14:31:54 CST,,0,LOG,00000,"archiver process (PID 8659) exited with exit code 1",,,,,,,,,""
2018-11-30 14:33:24.274 CST,,,8706,"192.168.56.92:34506",5c00d9b4.2202,1,"",2018-11-30 14:33:24 CST,,0,LOG,00000,"connection received: host=192.168.56.92 port=34506",,,,,,,,,""
2018-11-30 14:33:24.279 CST,"repl","",8706,"192.168.56.92:34506",5c00d9b4.2202,2,"",2018-11-30 14:33:24 CST,,0,FATAL,57P03,"the database system is shutting down",,,,,,,,,""
2018-11-30 14:33:24.292 CST,,,8652,,5c00d95a.21cc,5,,2018-11-30 14:31:54 CST,,0,LOG,00000,"database system is shut down",,,,,,,,,""

pg_ctl kill HUP

# /etc/init.d/postgresql restart
# ps -ef|grep -i post|grep -v grep
postgres  8746     1  0 14:37 ?        00:00:00 /usr/lib/postgresql/9.6/bin/postgres -D /data/pg9.6/main -c config_file=/etc/postgresql/9.6/main/postgresql.conf
postgres  8747  8746  0 14:37 ?        00:00:00 postgres: 9.6/main: logger process   
postgres  8752  8746  0 14:37 ?        00:00:00 postgres: 9.6/main: checkpointer process   
postgres  8753  8746  0 14:37 ?        00:00:00 postgres: 9.6/main: writer process   
postgres  8754  8746  0 14:37 ?        00:00:00 postgres: 9.6/main: wal writer process   
postgres  8755  8746  0 14:37 ?        00:00:00 postgres: 9.6/main: autovacuum launcher process   
postgres  8756  8746  0 14:37 ?        00:00:00 postgres: 9.6/main: archiver process   
postgres  8757  8746  0 14:37 ?        00:00:00 postgres: 9.6/main: stats collector process   
postgres  8803  8746  0 14:37 ?        00:00:00 postgres: 9.6/main: wal sender process repl 192.168.56.92(34610) streaming 0/20000178
postgres  8804  7488  0 14:37 pts/0    00:00:00 /usr/lib/postgresql/9.6/bin/psql
postgres  8812  8746  0 14:37 ?        00:00:00 postgres: 9.6/main: postgres postgres [local] idle

$ pg_ctl kill HUP 8746

2018-11-30 14:38:59.359 CST,,,8746,,5c00daa9.222a,3,,2018-11-30 14:37:29 CST,,0,LOG,00000,"received SIGHUP, reloading configuration files",,,,,,,,,"

pg_ctl kill ABRT

# /etc/init.d/postgresql restart
# ps -ef|grep -i post|grep -v grep
postgres  8848     1  0 14:41 ?        00:00:00 /usr/lib/postgresql/9.6/bin/postgres -D /data/pg9.6/main -c config_file=/etc/postgresql/9.6/main/postgresql.conf
postgres  8849  8848  0 14:41 ?        00:00:00 postgres: 9.6/main: logger process   
postgres  8851  8848  0 14:41 ?        00:00:00 postgres: 9.6/main: checkpointer process   
postgres  8852  8848  0 14:41 ?        00:00:00 postgres: 9.6/main: writer process   
postgres  8853  8848  0 14:41 ?        00:00:00 postgres: 9.6/main: wal writer process   
postgres  8854  8848  0 14:41 ?        00:00:00 postgres: 9.6/main: autovacuum launcher process   
postgres  8855  8848  0 14:41 ?        00:00:00 postgres: 9.6/main: archiver process   
postgres  8856  8848  0 14:41 ?        00:00:00 postgres: 9.6/main: stats collector process   
postgres  8895  8848  0 14:41 ?        00:00:00 postgres: 9.6/main: wal sender process repl 192.168.56.92(34614) streaming 0/21000098
postgres  8896  7488  0 14:41 pts/0    00:00:00 /usr/lib/postgresql/9.6/bin/psql
postgres  8904  8848  0 14:41 ?        00:00:00 postgres: 9.6/main: postgres postgres [local] idle


$ pg_ctl kill ABRT 8848


2018-11-30 14:42:32.934 CST,"repl","",8895,"192.168.56.92:34614",5c00dba8.22bf,3,"streaming 0/210000D0",2018-11-30 14:41:44 CST,,0,LOG,00000,"disconnection: session time: 0:00:48.066 user=repl database= host=192.168.56.92 port=34614",,,,,,,,,"walreceiver"
2018-11-30 14:42:32.943 CST,"postgres","postgres",8904,"[local]",5c00dbab.22c8,3,"idle",2018-11-30 14:41:47 CST,3/0,0,FATAL,57P01,"terminating connection due to unexpected postmaster exit",,,,,,,,,"psql"
2018-11-30 14:42:32.943 CST,"postgres","postgres",8904,"[local]",5c00dbab.22c8,4,"idle",2018-11-30 14:41:47 CST,,0,LOG,00000,"disconnection: session time: 0:00:45.196 user=postgres database=postgres host=[local]",,,,,,,,,"psql"

pg_ctl kill USR1
pg_ctl kill USR2

试了没啥日志输出，今天先这样，后面再补充。

总结：

pg_ctl kill TERM pid   = pg_ctl stop -m smart
pg_ctl kill INT pid    = pg_ctl stop -m fast
pg_ctl kill QUIT pid   = pg_ctl stop -m immediate
pg_ctl kill HUP pid    = pg_ctl reload
pg_ctl kill ABRT pid   = 类似于关闭电源
pg_ctl kill USR1 pid   = 
pg_ctl kill USR2 pid   =
数据库人生
关注
专栏目录
【0244】pg_ctl停止postmaster守护进程的底层实现原理
专注【PostgreSQL源码学习&研究】
01-18 224
本文将详细讲解pg_ctl命令停止一个运行中的PG服务的底层实现原理。正文内容将详细分为以下几个点：pg_ctl命令停止PG服务的几种方式postmaster守护进程是如何知晓pg_ctl命令发出的停止服务请求postmaster守护进程如何响应pg_ctl命令的不同停止命令postmaster停止服务的详细过程postmaster停止服务过程中与哪些文件相关？如何处理pg_ctl停止PG服务遇到failed报错，如何应对？围绕以上几点，从PG V13.2源码角度详细展开讨论本文的主题。
postgresql常用命令帮助
kmblack1的专栏
09-16 1515
postgresql常用命令帮助
KingbaseES 数据库无响应问题分析
最新发布
lyu1026的博客
07-26 334
一、背景及理论阐述 某项目数据库系统是集群环境，主库业务卡顿，应用反馈部分业务无法正常进行。 在操作系统中，物理内存(RAM)是有限的资源，当内存需求超过物理内存的容量时，操作系统会使用页面调度机制来管理内存资源。页面调度涉及将不常用的内存页面(Page)移到磁盘上的交换空间(Swap Space)或文件缓存中，以释放物理内存供其他进程使用。当需要再次访问这些页面时，它们会被从磁盘中读回内存。 ...
postgresql 杀不死的会话
一醉轻王侯的技术博客
05-25 2781
正常情况下， 第一种、第二种方式即可杀死： 第一种是： SELECT pg_cancel_backend(PID); 这种方式只能kill select查询，对update、delete 及DML不生效) 第二种是： SELECT pg_terminate_backend(PID); 这种可以kill掉各种操作(select、update、delete、drop等)操作 kill -SIGINT 或者 kill -SIGTERM 等同于以上两种 kill https://serverfault.com/q
Backtrack5的Postpresql的使用
iteye_14896的博客
03-03 347
Backtrack5的Postpresql的使用 在使用Backtrack5的Postpresql时发现没法正常连接进去，出现如下错误 -----------------------------------------------------------------------------------------------------   msf > db_connect po...
【PostgreSQL】PostgreSQL常用备份方法_received smart shutdown request
2401_84264010的博客
04-13 540
外链图片转存中…(img-r8h3a5Ui-1713000751548)][外链图片转存中…(img-CEnxCZuG-1713000751549)][外链图片转存中…(img-JmBMIHZI-1713000751549)][外链图片转存中…(img-gmMxkAL3-1713000751550)]
psql: 致命错误: 57P03: 数据库系统启动中
HighGO
12-04 3186
目录 环境 症状 问题原因 解决方案 环境 系统平台：Linux x86-64 Red Hat Enterprise Linux 7 版本：4.7.7 症状 pg_ctl start启动数据库后，运行psql报错：“psql: 致命错误: 57P03: 数据库系统启动中” [highgo@host data]$ pg_ctl start server starting [highgo@host data]$日志: 00000: This is a trial...
服务器显示PG,pg_ctl控制服务器
weixin_32352213的博客
08-10 648
pg_ctl 是一个用于初始化、启动、停止或控制PostgreSQL服务器的工具.使用方法:pg_ctl init[db] [-D 数据目录] [-s] [-o "选项"]pg_ctl start [-w] [-t 秒数] [-D 数据目录] [-s] [-l 文件名] [-o "选项"]pg_ctl stop [-w] [-t 秒数] [-D 数据目录] ...
pg_ctl -- 启动、停止、重启 PostgreSQL
热门推荐
Draco
08-03 6万+
pg_ctl 名称 pg_ctl -- 启动、停止、重启 PostgreSQL 语法 pg_ctl start [-w] [-s] [-D datadir] [-l filename] [-o options] [-p path] pg_ctl stop [-W] [-s] [-D datadir] [-m s[mart] | f[ast] | i[mmediate] ]
PostgreSQL备份与恢复（第一章）
PostgreSQL China
08-16 693
作者：徐田原 引言 PostgreSQL官方文档指定了以下三种备份方法，详见：https://www.postgresql.org/docs/current/backup.html -「SQL转储」，用pg_dump或pgdump_all进行备份，也是一种逻辑备份的方法，这种方法很容易操作，但是缺点就是一旦数据库太大，导入导出文件的效率就会降低。但是有了并行备份恢复和split拆分，也可以在这方面稍微优化。另一个缺点是无法恢复到故障发生的时刻。例如，你使用crontab定时任务在凌晨3点进行备份，结果12点
【0205】哪些信号可kill掉postmaster？内核如何实现？
专注【PostgreSQL源码学习&研究】
06-09 1285
中，详细讲解了PG数据库中postmaster，包括它所扮演的角色、负责功能等。本文内容将讲解不借助pg_ctl，而是通过信号的情况下，去（正常）停止正在运行中的PG服务。注意，变量名是必需的，因为它在原型和定义中都要使用。还要注意它的长名称。由于信号的注册过程已经掌握，那么接下来的重点就是信号注册的回调函数。中讲解的非常详细，如果你不清楚，则需要详细阅读此文章。该宏“是用作信号处理程序的参数列表。，则是采取信号默认的忽略处理方式。参数以外的其他参数的端口都应该在其。是如何实现信号的注册，这个在。
PG_ctl管理Postgresql数据库
kwame211的博客
11-03 1637
pg_ctl 名称：一个初始化，启动，停止，或控制PostgreSQL服务器的设备(命令). 用法：     pg_ctl init[db] [-D DATADIR] [-s] [-o "OPTIONS"]     pg_ctl start [-w] [-t SECS] [-D DATADIR] [-s] [-l FILENAME] [-o "OPTIONS"]
PostgreSQL12.3安装操作手册
君子不怨天的博客
08-17 1229
上传源码包（postgresql-12.3.tar.gz）到。OS环境：操作系统最小化安装,和开发工具包。创建挂载目录并清理YUM缓存。
重启postgre_postgresql如何重启
weixin_33831334的博客
01-17 8094
启动一个postgres最简单的方法是使用postgres命令(执行前请确认data目录已经被初始化完成)服务器必须由PostgreSQL用户帐户运行,而不是由root用户或任何其他用户运行,所以先确认切换为postgres用户postgres@me:/usr/local/pgsql$./bin/postgres-D./data这个命令使得数据库在前台运行,为了使得运维数据库更加方便,包装程...
Postgresql备库复制冲突原理
InternalsOf
04-01 4359
1 总结 报错类似于这样： FATAL: terminating connection due to conflict with recovery DETAIL: User query might have needed to see row versions that must be removed. HINT: In a moment you should be able to ...
PostgreSQL 切勿kill -9去杀进程
Focus on PostgreSQL
07-13 3658
熟悉Oracle的人可能会去经常使用kill -9杀进程，因为有的时候使用SQL命令去杀进程,一些进程的状态只是会被置为"killed"状态，其锁定的资源仍然没有释放，可能会收到提示： ORA-00031: session marked for kill 因此甚至还建议大家去使用kill -9直接去操作系统上杀掉进程。 又比如我们Oracle停库的时候常常都是先停监听，再手动kill掉LOCAL=NO的进程，然后再去停库。 但是要注意了，切勿在PostgreSQL中使用kill -9去杀掉进程！ 首先我们
pg_ctl：未找到命令
05-30
这个错误提示通常是因为 `pg_ctl` 命令没有被正确安装或者没有被正确添加到系统的 PATH 环境变量中。 首先，你可以使用以下命令检查 `pg_ctl` 命令是否存在： ```shell which pg_ctl ``` 如果该命令没有被安装，可以尝试使用以下命令安装 PostgreSQL 客户端工具： ```shell sudo apt-get install postgresql-client ``` 如果该命令已经被安装，可以尝试将 `pg_ctl` 命令所在的目录添加到系统的 PATH 环境变量中，例如： ```shell export PATH=$PATH:/usr/lib/postgresql/<version>/bin ``` 其中，`<version>` 是你安装的 PostgreSQL 版本号，例如 `10`, `11`, `12` 等。上述命令将 `/usr/lib/postgresql/<version>/bin` 目录添加到了系统的 PATH 环境变量中，这样在终端中就可以直接使用 `pg_ctl` 命令了。如果你希望该命令永久生效，可以将上述命令添加到你的 shell 配置文件（例如 `.bashrc` 或者 `.zshrc`）中。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

数据库人生

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值