| From: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | michael(at)paquier(dot)xyz |
| Cc: | kuntalghosh(dot)2007(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Regression test PANICs with master-standby setup on same machine |
| Date: | 2019-04-23 08:27:29 |
| Message-ID: | 20190423.172729.145755894.horiguchi.kyotaro@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Tue, 23 Apr 2019 14:53:28 +0900, Michael Paquier <michael(at)paquier(dot)xyz> wrote in <20190423055328(dot)GK2712(at)paquier(dot)xyz>
> On Tue, Apr 23, 2019 at 01:33:39PM +0900, Kyotaro HORIGUCHI wrote:
> > I think this is rahter a testing or debugging feature. This can
> > be apply to all paths, so the variable might be "path_prefix" or
> > something more generic than tablespace_chroot.
> >
> > Does it make sense?
>
> A GUC which enforces object creation does not sound like a good idea
> to me, and what you propose would still bite back, for example two
> local nodes could use the same port, but a different Unix socket
> path.
It's not necessarily be port number, but I agree that it's not a
good idea. I prefer allowing relative paths for tablespaces.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2019-04-23 08:44:18 | Re: Regression test PANICs with master-standby setup on same machine |
| Previous Message | Peter Eisentraut | 2019-04-23 08:23:23 | Re: Why does ExecComputeStoredGenerated() form a heap tuple |