Re: how can we resolving locking state ....

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: 노현석 <noh019(at)naver(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: how can we resolving locking state ....
Date: 2010-08-05 19:08:29
Message-ID: AANLkTimDcPP2RmbeVQvHN0MaGccOXzPgbrGRZcbFkBTO@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Please post in plain text if possible.

2010/8/5 노현석 <noh019(at)naver(dot)com>
>
> hi..
>
> we test locking PostgreSQL 8.4.4 on x86_64.
> $
> $ kill -9 5143

What you want is plain old

kill 5143
or
kill -SIGTERM 5143

Kill -SIGTERM is like using a fly swatter to kill a fly. SIGKILL (-9)
is like lobbing a grenade in the same room to kill said fly.

Note that in 8.4 and up there's a pg function to do this. 8.3 and
before kill -SIGTERM is what you want.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2010-08-05 19:43:58 Re: Why create CHECKPOINT_WAIT checkpoint in pg_start_backup not CHECKPOINT_IMMEDIATE?
Previous Message Andreas 'ads' Scherbaum 2010-08-05 18:03:46 Re: how can we resolving locking state....