Hackers,
One of our clients is seeing an unusual issue with statements which are
waiting going into sleep forever and never completing. This first
e-mail is for a has anyone else seen this problem before? while we try
to collect additional information for a diagnosis.
This problem only happens
Excerpts from Josh Berkus's message of jue ene 20 18:05:15 -0300 2011:
One of our clients is seeing an unusual issue with statements which are
waiting going into sleep forever and never completing. This first
e-mail is for a has anyone else seen this problem before? while we try
to
I have seen it -- on 8.1 too. On our case it was caused by an insert
that was doing lots of toast insertions, so it needed to grab the
extension lock frequently for the toast table; and this was slowed
down by a largish shared_buffers setting, somehow (8.1 doesn't have lock
partitioning, so
Josh Berkus j...@agliodbs.com writes:
One of our clients is seeing an unusual issue with statements which are
waiting going into sleep forever and never completing. This first
e-mail is for a has anyone else seen this problem before? while we try
to collect additional information for a
I would take that to mean that it's waiting on the client.
You mean that the client timed out and isn't accepting data from the
query anymore? Shouldn't Postgres time out on that after a while? In
one case, the orphaned statement was 16 hours old before we killed it.
If it's relevant, the
Josh Berkus j...@agliodbs.com writes:
I would take that to mean that it's waiting on the client.
You mean that the client timed out and isn't accepting data from the
query anymore?
No, if the backend is in RECV state, it's waiting for the client to
*send* it something.
(Although if this is
On 1/20/11 2:26 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
I would take that to mean that it's waiting on the client.
You mean that the client timed out and isn't accepting data from the
query anymore?
No, if the backend is in RECV state, it's waiting for the client to
