| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | 菊池祐 <y(dot)kikuchi0714(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: About pg_basebackup |
| Date: | 2022-05-19 06:57:14 |
| Message-ID: | 34e97beb7f8e2afbe463b42dced0d6b73364e568.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2022-05-19 at 13:18 +0900, 菊池祐 wrote:
> 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)
I guess that your "archive_command" is hanging or failing.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2022-05-19 07:10:04 | Re: In case of network issues, how long before archive_command does retries |
| Previous Message | 菊池祐 | 2022-05-19 04:18:35 | About pg_basebackup |