Re: Bugs during ProcessCatchupEvent() - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Bugs during ProcessCatchupEvent()
Date
Msg-id 1231254709.15005.52.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Bugs during ProcessCatchupEvent()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bugs during ProcessCatchupEvent()  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Tue, 2009-01-06 at 09:44 -0500, Tom Lane wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
> > It looks to me that generating a single error message while idle causes
> > the server to provide ErrorResponse, which the client assumes is the end
> > of the processing of that statement as defined in FE/BE protocol.
> 
> Yeah.  I think this is actually a client-side issue: it should keep
> reading till it gets a 'Z' message.  Not clear how that fits into the
> libpq-to-app API though.

That makes sense. I'll dig around there.


The infinite loop error seems server-side though.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Hot Standby Query Conflicts
Next
From: Alvaro Herrera
Date:
Subject: Re: QuickLZ compression algorithm (Re: Inclusion in the PostgreSQL backend for toasting rows)