| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bugs during ProcessCatchupEvent() |
| Date: | 2009-01-06 15:11:49 |
| Message-ID: | 1231254709.15005.52.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2009-01-06 at 09:44 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)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.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-01-06 15:16:10 | Re: lazy_truncate_heap() |
| Previous Message | Alvaro Herrera | 2009-01-06 15:11:27 | Re: QuickLZ compression algorithm (Re: Inclusion in the PostgreSQL backend for toasting rows) |