From: | Dhruv Shukla <dhruvshukla82(at)gmail(dot)com> |
---|---|
To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
Cc: | "jayknowsunix(at)gmail(dot)com" <jayknowsunix(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Problems with PG 9.3 |
Date: | 2014-08-25 15:04:58 |
Message-ID: | CAFiWeJBppWiDKBgN49WpFgGrRYw3tG9W=gsjNkZTNwmEafX1=g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
We have a script which notifies us if there are any locks that its waiting
for and it sends an email out. But nothing has came thru ...
here is one pid which has got stuck from midnight and is still running, but
doesnt seem like it will finish anytime soon. It was run manually by me
using an strace.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
64144 postgres 20 0 81.2g 4.1g 4.1g R 100.0 1.1 537:59.86 postmaster
I even checked the lock scripts by running each of the query but nothing
has came thru.
https://wiki.postgresql.org/wiki/Lock_Monitoring
Cent OS 6.3, Postgres 9.3.3, Postgis.
On Mon, Aug 25, 2014 at 1:54 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
wrote:
> Dhruv Shukla wrote:
> > Right now we are doing is only logs where on each statement for a sql
> function we are raising an info.
> >
> > This way we know which step its getting stuck. Today it got stuck on the
> insert statement.
> >
> > And we ran the same SQL function after killing the process, it ran
> normal without any issues.
>
> That sounds a lot like locking problems.
>
> Examine pg_locks when a process gets stuck an see if it is waiting for a
> lock
> and who is holding the lock.
>
> Yours,
> Laurenz Albe
>
--
Regards
Dhruv
404-551-2578
From | Date | Subject | |
---|---|---|---|
Next Message | Dhruv Shukla | 2014-08-25 15:14:45 | Re: Problems with PG 9.3 |
Previous Message | Horst Düster | 2014-08-25 12:36:42 | Re: Database User Quota |