RE: BUG #16003: pg_basebackup failed with error : directory "xxxxxxx" exists but is not empty

Поиск
Список
Период
Сортировка
От RUIZ Sébastien
Тема RE: BUG #16003: pg_basebackup failed with error : directory "xxxxxxx" exists but is not empty
Дата
Msg-id PR0P264MB041012580F2952DB0C07B148A5B30@PR0P264MB0410.FRAP264.PROD.OUTLOOK.COM
обсуждение исходный текст
Ответ на Re: BUG #16003: pg_basebackup failed with error : directory "xxxxxxx" exists but is not empty  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-bugs
Дерево обсуждения

Ok, thanks for the answer and the advice.

This thread can be closed.

best regards.

 

 

Cordialement, 

cid:image001.jpg@01D35FC5.0989FAF0

 

Sébastien RUIZ

Administrateur Bases de Données

Direction de la  Production et des Infrastructures

Direction des Opérations et de la Transformation 

cid:image010.jpg@01D373FE.EBC9E180 02 47 46 53 84 – Bât. A - Bureau 114

41, rue Fabienne Landy 37700 ST PIERRE DES CORPS

 

cid:image005.gif@01D35FC5.0989FAF0cid:image006.gif@01D35FC5.0989FAF0cid:image007.gif@01D35FC5.0989FAF0cid:image008.gif@01D35FC5.0989FAF0cid:image009.gif@01D35FC5.0989FAF0www.harmonie-mutuelle.fr

 

 

De : Magnus Hagander <magnus@hagander.net>
Envoyé : vendredi 13 septembre 2019 15:17
À : RUIZ Sébastien <Sebastien.RUIZ@harmonie-mutuelle.fr>
Cc : pgsql-bugs@lists.postgresql.org
Objet : Re: BUG #16003: pg_basebackup failed with error : directory "xxxxxxx" exists but is not empty

 

 

 

On Fri, Sep 13, 2019 at 4:28 AM RUIZ Sébastien <Sebastien.RUIZ@harmonie-mutuelle.fr> wrote:

Hi Magnus,

 

Thanks for the reply.

 

We have tablespace directories inside other tablespaces because we have a technical schema (call »tech) into each database.

So we can’t put thoses tablespaces (for tech) anywhere else (they have the same name).

 

I don't understand that argument. The only *reason* to have multiple tablespaces is to put them in different locations. If you put them in the same location, why have them at all? Just move everything to the main tablespace and remove them.

 

You can have an unlimited (more or less) number of schemas in the same database, in the same tablespace. There is no connection whatsoever between schemas and tablespaces.

 

 

Well… it’s our choice. Probably it’s not a good choice but it’s done and it will be very difficult to change this actually. 

 

But do you think it’s impossible for dev team to change pg_basebackup so that it works in this case ? 

 

Nothing is impossible. Worse case you could always have a fork created for your specific environment. But compared to either of those options it will be easier to actually fix your installation.

 

 

 

(by the way, i’m not sure it’s the right way to answer like this (reply this mail) for the comunication on this list. I don’t know how i can do  otherwise…)

 

That is definitely the correct way.

 

 

//Magnus

 

Вложения

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: BUG #16003: pg_basebackup failed with error : directory "xxxxxxx" exists but is not empty
Следующее
От: Kiran Khatke
Дата:
Сообщение: Re: BUG #16007: Regarding patch for BUG #3995: pqSocketCheck doesn't return