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-29T23:23:08Z
Lists: pgsql-hackers
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.

However, that's only addressing the reporting end of it; I think we
also need to change the pg_upgrade test script as suggested by Noah.

			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 →
  1. Refactor flex and bison make rules