From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Bugs during ProcessCatchupEvent() |
Date: | 2009-02-04 19:53:53 |
Message-ID: | 200902041953.n14JrrD11942@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs wrote:
>
> 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.
Any progress on this?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Kenneth Marshall | 2009-02-04 19:57:57 | Re: <note> on hash indexes |
Previous Message | Bruce Momjian | 2009-02-04 19:52:40 | Re: TODO items for window functions |