pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: 菊池祐 <y.kikuchi0714@gmail.com>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: About pg_basebackup
Date: Thu, 19 May 2022 13:14:10 +0900
Message-ID: <87A19691-F8EE-4595-A974-DDC4FAFF88E8@gmail.com> (raw)
In-Reply-To: <CAKFQuwYGTio50YxkUaV5TpvLCM1sXQ8uxnwSfxRmECJJW4T0Jg@mail.gmail.com>
References: <CAKFQuwYGTio50YxkUaV5TpvLCM1sXQ8uxnwSfxRmECJJW4T0Jg@mail.gmail.com>

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.g.johnston@gmail.com> wrote:
> 
> 
>> On Wed, May 18, 2022 at 8:35 PM 菊池祐 <y.kikuchi0714@gmail.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.
> 

view thread (3+ messages)

Message-ID: <87A19691-F8EE-4595-A974-DDC4FAFF88E8@gmail.com>
Permalink:  ../87A19691-F8EE-4595-A974-DDC4FAFF88E8@gmail.com/
Also on:    postgresql.org/message-id/87A19691-F8EE-4595-A974-DDC4FAFF88E8@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: y.kikuchi0714@gmail.com, david.g.johnston@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: About pg_basebackup
  In-Reply-To: <87A19691-F8EE-4595-A974-DDC4FAFF88E8@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox