Bill Moran writes:
> I do wonder what else is happening in the transaction that you're
> calling NOTIFY within; and that some other statement could be causing
> the lock wait.
FWIW, the lock seems to be the one taken to serialize insertions into
the shared NOTIFY queue, from this bit in commands/
I don't know the answer to your question. Please keep mailing list
conversations on the list, otherwise you won't get the benefit of
someone else who may know the answer.
I do wonder what else is happening in the transaction that you're
calling NOTIFY within; and that some other statement could
On Wed, Mar 13, 2013 at 8:08 AM, Aln Kapa wrote:
> 2013-03-10 14:27:43 19797 LOG: could not receive data from client:
> Connection reset by peer
> 2013-03-10 14:27:43 19797 LOG: unexpected EOF on client connection
>
> Tell me what's the problem?
>
Your client closed the socket without cleanly
On Thu, 14 Mar 2013 15:24:45 +0400 Aln Kapa wrote:
>
> I connect to the database using the PGDAC, and then send a NOTIFY to
> myself every minute. In this case, the logs get that.
>
> 2013-03-10 10:34:36 19797 LOG: process 19797 still waiting for
> AccessExclusiveLock on object 0 of class 1262
HI.
I connect to the database using the PGDAC, and then send a NOTIFY to
myself every minute. In this case, the logs get that.
2013-03-10 10:34:36 19797 LOG: process 19797 still waiting for
AccessExclusiveLock on object 0 of class 1262 of database 0 after
3000.100 ms
2013-03-10 10:34:36 19797 S
HI.
I connect to the database using the PGDAC, and then send a NOTIFY to
myself every minute. In this case, the logs get that.
2013-03-10 10:34:36 19797 LOG: process 19797 still waiting for
AccessExclusiveLock on object 0 of class 1262 of database 0 after
3000.100 ms
2013-03-10 10:34:36 19797 S
