| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: UUNET socket-file-location patch |
| Date: | 2000-11-13 17:33:52 |
| Message-ID: | 9928.974136832@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
I have to agree with Peter E. on this patch: it's poorly thought out.
I don't mind the idea of being able to relocate the socket file,
but the client-side interface they've chosen is silly. Having to
add another switch to every client app is not reasonable --- it's
bad enough that you had to hack every one of the clients we supply,
but what of client apps that just use libpq or one of the other
interface libraries? They'll be unable to talk to such a postmaster
without further work.
We should revert all the client-side changes from this patch, and
instead teach libpq and the other interfaces to treat a host name
that starts with a slash as being a path to a socket file (replacing
the default assumption of "/tmp"). Much cleaner, especially for
existing client apps.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-11-13 17:51:57 | Re: UUNET socket-file-location patch |
| Previous Message | Tom Lane | 2000-11-13 15:41:45 | Re: pgsql/src/backend/storage/smgr (smgr.c) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-11-13 17:38:13 | Re: Details for planned template0/template1 change |
| Previous Message | Philip Warner | 2000-11-13 17:28:04 | Re: Details for planned template0/template1 change |