Re: [HACKERS] Duplicate usage of tablespace location? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Duplicate usage of tablespace location?
Date
Msg-id 21084.1491494631@sss.pgh.pa.us
Whole thread Raw
Responses Re: [HACKERS] Duplicate usage of tablespace location?  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-hackers
Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.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



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: [HACKERS] Remove pg_stat_progress_vacuum from Table 28.2
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Faster methods for getting SPI results (460%improvement)