Re: Re: UUNET socket-file-location patch - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Re: UUNET socket-file-location patch
Date
Msg-id 200011160518.AAA26912@candle.pha.pa.us
Whole thread Raw
In response to Re: Re: UUNET socket-file-location patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Peter Eisentraut <peter_e@gmx.net> writes:
> > Tom Lane writes:
> >>>> and make "/tmp" the default in guc.c.
> >> 
> >> No, because this has to work on the client side too.  The default path
> >> *must* be determined at compile time, or clients and servers will be
> >> unable to find each other.
> 
> > The only difference between your snippet and mine is that yours sets the
> > default to "" and interprets it as "/tmp" when it is used, whereas mine
> > sets the default to "/tmp" to begin with.  Clients don't see the
> > difference.
> 
> Clients that don't contain guc.c are going to see a difference, no?
> Where are they getting the default from?

Good point.  This macro is called by the backend, and the libpq frontend
code.  We would have to push the /tmp default into libpq code too, which
seems messier.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: Re: Coping with 'C' vs 'newC' function language namesh
Next
From: Bruce Momjian
Date:
Subject: Re: 486 Optimizations...