From: | 菊池祐 <y(dot)kikuchi0714(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: About pg_basebackup |
Date: | 2022-05-19 04:14:10 |
Message-ID: | 87A19691-F8EE-4595-A974-DDC4FAFF88E8@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Thank you for quick response.
I’ll ask pgsql-general mailing list.
Best regards,
Yu
> On May 19, 2022, at 12:46, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>
>> On Wed, May 18, 2022 at 8:35 PM 菊池祐 <y(dot)kikuchi0714(at)gmail(dot)com> wrote:
>> Hi,
>>
>> I executed the pg_basebackup command to set up a replication configuration in postgresql, but the following message appears and replication didn’t complete.
>>
>> 2741/2742 tablespaces (/var/lib/pgsql/9.2/bac12609150596/12609150596 kB (100%), 2741/2742 tablespaces (/var/lib/pgsql/9.2/bac12609150596/12609150596 kB (100%), 2742/2742 tablespaces NOTICE: pg_stop_backup cleanup done, waiting for required WAL segments to be archived WARNING: pg_stop_backup still waiting for all required WAL segments to be archived (60 seconds elapsed) HINT: Check that your archive_command is executing properly. pg_stop_backup can be canceled safely, but the database backup will not be usable without all the WAL segments. WARNING: pg_stop_backup still waiting for all required WAL segments to be archived (120 seconds elapsed) ・ ・ ・
>>
>> Please let me know how to deal with this.
>>
>
> Impossible to say with the information provided. The PostgreSQL log file during this period should prove informative. You have an archive_command set so look for any messages indicating it is failing (just like the HINT says...)
>
> What specific version of the long unsupported version 9.2.x are you running?
>
> This seems unlikely to be a bug. Support questions are more appropriately directed to the pgsql-general mailing list.
>
> David J.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrey Borodin | 2022-05-19 04:22:44 | Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY |
Previous Message | David G. Johnston | 2022-05-19 03:46:15 | Re: About pg_basebackup |