Re: Overlength socket paths (was Re: [COMMITTERS] pgsql: Refactor flex and bison make rules)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Jeremy Drake <pgbuildfarm(at)jdrake(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Overlength socket paths (was Re: [COMMITTERS] pgsql: Refactor flex and bison make rules)
Date: 2012-11-30 00:20:53
Message-ID: 22387.1354234853@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Andrew Dunstan <andrew(at)dunslane(dot)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

Attachment Content-Type Size
check-socket-path-length.patch text/x-patch 3.1 KB

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2012-11-30 00:24:32 Re: Overlength socket paths (was Re: [COMMITTERS] pgsql: Refactor flex and bison make rules)
Previous Message Tom Lane 2012-11-30 00:16:14 Re: Overlength socket paths (was Re: [COMMITTERS] pgsql: Refactor flex and bison make rules)

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2012-11-30 00:24:32 Re: Overlength socket paths (was Re: [COMMITTERS] pgsql: Refactor flex and bison make rules)
Previous Message Tom Lane 2012-11-30 00:16:14 Re: Overlength socket paths (was Re: [COMMITTERS] pgsql: Refactor flex and bison make rules)