Re: Proof of concept: standalone backend with full FE/BE protocol

Andres Freund <andres@2ndquadrant.com>

From: Andres Freund <andres@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org, Noah Misch <noah@leadboat.com>, hlinnaka@iki.fi
Date: 2012-09-04T05:30:28Z
Lists: pgsql-hackers
On Tuesday, September 04, 2012 06:20:59 AM Tom Lane wrote:
> Andres Freund <andres@2ndquadrant.com> writes:
> > I can see why that would be nice, but is it really realistic? Don't we
> > expect some more diligence in applications using this against letting
> > such a child continue to run after ctrl-c/SIGTERMing e.g. pg_dump in
> > comparison to closing a normal database connection?
> 
> Er, what?  If you kill the client, the child postgres will see
> connection closure and will shut down.  I already tested that with the
> POC patch, it worked fine.
Well, but that will make scripting harder because you cannot start another 
single backend pg_dump before the old backend noticed it, checkpointed and 
shut down.

Andres
-- 
Andres Freund		http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services


Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Remove now redundant pgpipe code.