Duplicate usage of tablespace location?

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Duplicate usage of tablespace location?
Date: 2017-04-06 07:08:44
Message-ID: 20170406.160844.120459562.horiguchi.kyotaro@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


I noticed by the following report, PostgreSQL can share the same
directory as tablespaces of two servers with different


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.

This is apparently a bug but doesn't cause any other problem
immediately. If we choose not to do this, the documentaion needs
to be edited instead.


| The location must be an existing, empty directory that is owned
| by the PostgreSQL operating system user.


Kyotaro Horiguchi
NTT Open Source Software Center

Attachment Content-Type Size
check_tsdir_emptiness.patch text/x-patch 1.2 KB


Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2017-04-06 07:14:13 Re: Declarative partitioning vs. information_schema
Previous Message Petr Jelinek 2017-04-06 07:04:06 Re: PoC plpgsql - possibility to force custom or generic plan