Re: Proof of concept: standalone backend with full FE/BE protocol
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org, Noah Misch <noah@leadboat.com>, hlinnaka@iki.fi
Date: 2012-09-04T04:20:59Z
Lists: pgsql-hackers
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. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Remove now redundant pgpipe code.
- d2c1740dc275 9.2.0 cited