Thank you for your reply.
On Wed, 25 Apr 2007 10:22:25 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > takuya koide wrote:
> >> 4) send 'SIGSTOP' signal to postgres
>
> > If you "stop" a process by SIGSTOP you must make it run again with
> > SIGCONT. O
Thank you for your reply.
On Wed, 25 Apr 2007 09:44:47 -0400
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> 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 ?
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> takuya koide wrote:
>> 4) send 'SIGSTOP' signal to postgres
> 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.
S
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 ?S18:48 0:00
> /usr/bin/postmaster -p 5432 -D /var/lib/pgsql/data
> postgres 3509 0.0 0.2 11132 568
