Re: Orphaned statements issue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Orphaned statements issue
Date: 2011-01-20 22:26:13
Message-ID: 22341.1295562373@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)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 an SSL connection, it's a bit harder to be sure
about what the logical state of the connection is.)

> Shouldn't Postgres time out on that after a while?

Not if the problem is the client is confused. As long as the remote-end
kernel doesn't indicate the connection is dead, we'll wait for the
client to wake up and send us a command.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Farina 2011-01-20 22:28:15 One Role, Two Passwords
Previous Message Josh Berkus 2011-01-20 22:09:16 Re: SSI and Hot Standby