Bruce Momjian writes:
> Andrew - Supernews wrote:
>> What's _not_ a good idea is ignoring the EPIPE error from write(), which
>> seems to currently be reported via ereport(COMMERROR) which doesn't try
>> and abort the query as far as I can tell.
> Where are you seeing this? I looked from Postgre
Andrew - Supernews wrote:
> On 2005-05-01, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> > The problem, as I understand it, is that if you have a long-running
> > query and the client process disappears, the query keeps running and
> > holds whatever resources it may have until it finishes. In f
On 2005-05-01, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> The problem, as I understand it, is that if you have a long-running
> query and the client process disappears, the query keeps running and
> holds whatever resources it may have until it finishes. In fact, it
> keeps sending data to t
