From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Duplicate usage of tablespace location? |
Date: | 2017-04-06 16:03:51 |
Message-ID: | 21084.1491494631@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> writes:
> I noticed by the following report, PostgreSQL can share the same
> directory as tablespaces of two servers with different
> pg-versions.
> https://www.postgresql.org/message-id/2008148.rxBNyNRHPZ@peanuts2
> 8.4 checked that the tablespace location is empty, but from 9.0,
> the check is replaced with creating a PG_PGVER_CATVER
> subdirectory. This works for multiple servers with the same
> version, but don't for servers with different versions.
Please explain why you think it doesn't work. This patch seems to
be reverting an intentional behavioral change, and you haven't
really explained why we'd want to. It certainly doesn't look like
it addresses the referenced complaint about pg_basebackup behavior.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-04-06 16:04:45 | Re: Faster methods for getting SPI results (460% improvement) |
Previous Message | Fujii Masao | 2017-04-06 15:56:59 | Re: Remove pg_stat_progress_vacuum from Table 28.2 |