pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
About pg_basebackup
3+ messages / 2 participants
[nested] [flat]

* About pg_basebackup
@ 2022-05-19 03:35  菊池祐 <y.kikuchi0714@gmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: 菊池祐 @ 2022-05-19 03:35 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org

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.

The environment is as follows and I attached postgresql.conf file.

Version : 9.2

OS : Cent 6.6

Attachments:

  -6124946774920295119postgresql.conf (application/octet-stream, 26.3K) download

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: About pg_basebackup
@ 2022-05-19 03:46  David G. Johnston <david.g.johnston@gmail.com>
  parent: 菊池祐 <y.kikuchi0714@gmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: David G. Johnston @ 2022-05-19 03:46 UTC (permalink / raw)
  To: 菊池祐 <y.kikuchi0714@gmail.com>; +Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>

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.

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: About pg_basebackup
@ 2022-05-19 04:14  菊池祐 <y.kikuchi0714@gmail.com>
  parent: David G. Johnston <david.g.johnston@gmail.com>
  0 siblings, 0 replies; 3+ messages in thread

From: 菊池祐 @ 2022-05-19 04:14 UTC (permalink / raw)
  To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>

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.
> 

^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2022-05-19 04:14 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-05-19 03:35 About pg_basebackup 菊池祐 <y.kikuchi0714@gmail.com>
2022-05-19 03:46 ` David G. Johnston <david.g.johnston@gmail.com>
2022-05-19 04:14   ` 菊池祐 <y.kikuchi0714@gmail.com>

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