On 11/13/2016 11:52 PM, Yogesh Sharma wrote:
you can look those relation numbers up in the pg_catalog to see what they are.
you can see what the processes are in pg_stat_activity.
Currently machine is not available. Please suggest if any other approach to
identify the same.
without
ral-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: Monday, November 14, 2016 4:19 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Request to share information regarding deadlock in
postgresql-8.1.18
On 11/13/2016 11:01 PM, Yogesh Sharma w
On 11/13/2016 11:01 PM, Yogesh Sharma wrote:
DETAIL: Process 12345 waits for AccessShareLock on relation 16446 of database
16385; blocked by process 23136.
Process 23136 waits for ShareLock on relation 16482 of database 16385; blocked
by process 12345.
you have two processes that are each
Dear All,
Thanks in advance.
In my Linux system, below error is found and after 10~12 hours, WAL file in
pg_xlog directory are increased continuously.
PostgreSQL:ERROR: deadlock detected
DETAIL: Process 12345 waits for AccessShareLock on relation 16446 of database
16385; blocked by process
