Re: Proof of concept: standalone backend with full FE/BE protocol
Jim Nasby <jim@nasby.net>
From: Jim Nasby <jim@nasby.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Date: 2012-09-07T21:47:49Z
Lists: pgsql-hackers
On 9/2/12 7:23 PM, Tom Lane wrote: > 4. As coded, the backend assumes the incoming pipe is on its FD 0 and the > outgoing pipe is on its FD 1. This made the command line simple but I'm > having second thoughts about it: if anything inside the backend tries to > read stdin or write stdout, unpleasant things will happen. It might be > better to not reassign the pipe FD numbers. In that case we'd have to > pass them on the command line, so that the syntax would be something > like "postgres --child 4,5 -D pgdata ...". Would it be sufficient to just hard-code the FD's to use? I'm not sure why someone would need to change them, so long as we steer clear of STD(IN|OUT|ERR)... -- Jim C. Nasby, Database Architect jim@nasby.net 512.569.9461 (cell) http://jim.nasby.net
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