Re: pg_basebackup + SSL error: bad length
| От | Csaba Ragasits |
|---|---|
| Тема | Re: pg_basebackup + SSL error: bad length |
| Дата | |
| Msg-id | CANaXbVhLXdmFfCNBpXh+s+6RgnqOt8UHJDtk+bBvpFiKfbt38A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pg_basebackup + SSL error: bad length (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: pg_basebackup + SSL error: bad length
|
| Список | pgsql-general |
Hello,
Only one copy is from the pg_basebackup on the machines.
I have only a tablespace only a different location:
/srv/pgdata/tbs_int303
I think I solved the problem:
When I delete manually the /srv/pgdata/tbs_int303 folder, the pg_basebackup is running fine.
I have only a tablespace only a different location:
/srv/pgdata/tbs_int303
I think I solved the problem:
When I delete manually the /srv/pgdata/tbs_int303 folder, the pg_basebackup is running fine.
Thank you for your help,
Csaba
2018-08-28 4:49 GMT+02:00 Michael Paquier <michael@paquier.xyz>:
On Mon, Aug 27, 2018 at 04:40:34PM -0700, Adrian Klaver wrote:
> Is there more then one copy of pg_basebackup on the machines?
Or this user has created a tablespace directly in the main data folder,
which can cause pg_basebackup to fail because of recursion issues. It
is no wonder that a WARNING is created during a CREATE TABLESPACE if you
do that.
--
Michael
В списке pgsql-general по дате отправления: