Re: Test "tablespace" fails during `make installcheck` on master-replica setup

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Test "tablespace" fails during `make installcheck` on master-replica setup
Date: 2016-12-07 15:06:10
Message-ID: 28347.1481123170@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> It would be really nice if we would detect that some other postmaster is
> already using a given tablespace directory and to throw an error and
> complain rather than starting up thinking everything is fine.

In principle, we could have the postmaster run through $PGDATA/pg_tblspc
and drop a lockfile into each referenced directory. But the devil is in
the details --- in particular, not sure how to get the right thing to
happen during a CREATE TABLESPACE. Also, I kinda doubt that this is going
to fix anything for the replica-on-same-machine problem.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Erik Rijkers 2016-12-07 16:19:54 Re: Declarative partitioning - another take
Previous Message Peter Moser 2016-12-07 14:57:33 Re: [PROPOSAL] Temporal query processing with range types