Re: Overlength socket paths (was Re: [COMMITTERS] pgsql: Refactor flex and bison make rules)
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Jeremy Drake <pgbuildfarm@jdrake.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2012-11-30T00:20:53Z
Lists: pgsql-hackers
Attachments
- check-socket-path-length.patch (text/x-patch) patch
Tom Lane <tgl@sss.pgh.pa.us> writes: > Andrew Dunstan <andrew@dunslane.net> writes: >> ... Or maybe the >> postmaster needs to check the length somehow before it calls >> StreamServerPort() so we can give a saner error message. > Hm. That's ugly, but a lot less invasive than trying to get the > official API to pass the information through. Sounds like a plan to me. Here's a patch for that --- I think we should apply and back-patch this. 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 →
-
Refactor flex and bison make rules
- 8521d131941b 9.3.0 cited