takuya koide wrote:
> 4) send 'SIGSTOP' signal to postgres
> # kill -SIGSTOP 3619
> # ps axuw|grep -i postgres|grep -Ev 'grep|bash|su -'
> postgres 3507 0.0 1.1 21352 2804 ? S 18:48 0:00
> /usr/bin/postmaster -p 5432 -D /var/lib/pgsql/data
> postgres 3509 0.0 0.2 11132 568 ? S 18:48 0:00 postgres: logger process
> postgres 3514 0.0 0.3 21352 852 ? S 18:48 0:00 postgres: writer process
> postgres 3515 0.0 0.2 12132 564 ? S 18:48 0:00 postgres: stats buffer process
> postgres 3516 0.0 0.3 11364 772 ? S 18:48 0:00 postgres: stats collector process
> postgres 3618 0.0 0.6 8476 1752 pts/3 S+ 18:54 0:00 psql template1
> postgres 3619 0.0 0.8 22012 2124 ? T 18:54 0:00 postgres:
> postgres template1 [local] idle
If you "stop" a process by SIGSTOP you must make it run again with
SIGCONT. Otherwise it's just not processing signals, so it'll obviously
not shut down. I don't think this is a bug.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
