Tom Lane wrote:
Michael Akinde writes:
Tom Lane wrote:
In the past we've seen this type of thing caused by multithreaded
client programs in which more than one thread tried to use the same
PGconn object without adequate interlocking.
Our application is single-threaded, so it see
Michael Akinde writes:
> Tom Lane wrote:
>> In the past we've seen this type of thing caused by multithreaded
>> client programs in which more than one thread tried to use the same
>> PGconn object without adequate interlocking.
> Our application is single-threaded, so it seems unlikely that we a
Tom Lane wrote:
Michael Akinde writes:
Anyway - the situation now is that just the loading process is hanging
on the server, with an in transaction. But it is definitely the
loading program that is hanging, not the Postgres server.
What the stack traces seem to show is that both the
Michael Akinde writes:
> Anyway - the situation now is that just the loading process is hanging
> on the server, with an in transaction. But it is definitely the
> loading program that is hanging, not the Postgres server.
What the stack traces seem to show is that both the client and the
serve
Tom Lane wrote:
Hmm, can you attach to the stuck backend and the vacuum worker process
with gdb and get stack traces from them? The pg_locks view does not
indicate any locking problem, but I'm wondering if there could be a
deadlock at the LWLock level.
My reply seems to have been lost in the eth
Hej,
I killed the test about an hour ago to eliminate the free space stuff as
an issue. I've started the process up again, so if (when) the test hangs
again, I'll try to get the stack trace.
Regards,
Michael Akinde
Tom Lane wrote:
Michael Akinde writes:
We have been running into a stra
Michael Akinde writes:
> We have been running into a strange problem on our production servers of
> a system we are about to roll out with the loading of large objects.
Hmm, can you attach to the stuck backend and the vacuum worker process
with gdb and get stack traces from them? The pg_locks v
Hi,
We have been running into a strange problem on our production servers of
a system we are about to roll out with the loading of large objects. At
various times (usually separated by a few days), the loading process
against the server will suddenly either take an extremely long time
(going
