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 waiting for locks the other have.
process 12345 is waiting for relation (table) with OID 16446, that table
is blocked by process 23136
and process 23136 is waiting for a lock on another table, OID 16482,
which the first process has a lock on.
this is a logic error in your application.
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.
THis has nothing to do with the growing WAL logs... something is
blocking checkpoints if a single WAL file keeps growing, are you using
some form of wal archiving, is that working correctly ? could something
be preventing checkpoints? what are the related checkpoint and WAL
settings?
--
john r pierce, recycling bits in santa cruz
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
