Re: Fixing pg_basebackup with tablespaces found in $PGDATA
От | Michael Paquier |
---|---|
Тема | Re: Fixing pg_basebackup with tablespaces found in $PGDATA |
Дата | |
Msg-id | CAB7nPqQHOvT4pn1gRp5Gw3nq508E5wPzQo0F-c=pJWdbyureaA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Fixing pg_basebackup with tablespaces found in $PGDATA (Bernd Helmle <mailings@oopsware.de>) |
Список | pgsql-hackers |
On Thu, Jan 2, 2014 at 11:34 PM, Bernd Helmle <mailings@oopsware.de> wrote: > > > --On 1. Januar 2014 23:53:46 +0100 Dimitri Fontaine <dimitri@2ndQuadrant.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. Same here. +1 for fixing it. Having tablespaces in PGDATA itself is most of the time part of some obscure policy making easier to manage all the data in one folder... -- Michael
В списке pgsql-hackers по дате отправления: