Re: Bugs during ProcessCatchupEvent()

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
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 22:06:55
Message-ID: 1233785215.4500.340.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Wed, 2009-02-04 at 14:53 -0500, Bruce Momjian wrote:
> 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?

No, not had time in recent days.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zdenek Kotala 2009-02-04 22:22:44 Re: <note> on hash indexes
Previous Message David Fetter 2009-02-04 21:56:11 Re: Auto-updated fields