| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Subject: | Re: Fixing pg_basebackup with tablespaces found in $PGDATA |
| Date: | 2014-01-02 14:34:04 |
| Message-ID: | 490A525B2C76BE74B763F97C@apophis.credativ.lan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--On 1. Januar 2014 23:53:46 +0100 Dimitri Fontaine
<dimitri(at)2ndQuadrant(dot)fr> wrote:
> Hi,
>
> As much as I've seen people frown upon $subject, it still happens in the
> wild, and Magnus seems to agree that the current failure mode of our
> pg_basebackup tool when confronted to the situation is a bug.
>
> So here's a fix, attached.
I've seen having tablespaces under PGDATA as a policy within several data
centres in the past. The main reasoning behind this seems that they
strictly separate platform and database administration and for database
inventory reasons. They are regularly surprised if you tell them to not use
tablespaces in such a way, since they absorbed this practice over the years
from other database systems. So +1 for fixing this.
--
Thanks
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-01-02 14:40:54 | Re: preserving forensic information when we freeze |
| Previous Message | Tom Lane | 2014-01-02 14:28:19 | Re: more psprintf() use |