| From: | "Hamlin, Garick L" <ghamlin(at)isc(dot)upenn(dot)edu> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Unix-domain socket support on Windows |
| Date: | 2019-12-18 14:24:20 |
| Message-ID: | 20191218142419.fvv4ikm4wq4gnkco@isc.upenn.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 18, 2019 at 02:52:15PM +0100, Peter Eisentraut wrote:
> To implement this, tweak things so that setting DEFAULT_PGSOCKET_DIR
> to "" has the desired effect. This mostly already worked like that;
> only a few places needed to be adjusted. Notably, the reference to
> DEFAULT_PGSOCKET_DIR in UNIXSOCK_PATH() could be removed because all
> callers already resolve an empty socket directory setting with a
> default if appropriate.
Would it make sense to support abstract sockets in PostgreSQL?
I know it's bit unrelated. I haven't read all the code here I just was
thinking about it because of the code checking the leading \0 byte of the dir.
Garick
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-12-18 14:43:12 | Re: psql's EDITOR behavior on Windows |
| Previous Message | Tom Lane | 2019-12-18 14:14:25 | Re: jacana seems to be failing in recoverycheck from last few runs |