Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nrXZJ-00069o-7u for pgsql-bugs@arkaria.postgresql.org; Thu, 19 May 2022 04:15:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nrXYI-0005pG-9t for pgsql-bugs@arkaria.postgresql.org; Thu, 19 May 2022 04:14:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nrXYH-0005p6-Uy for pgsql-bugs@lists.postgresql.org; Thu, 19 May 2022 04:14:18 +0000 Received: from mail-pl1-x636.google.com ([2607:f8b0:4864:20::636]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nrXYF-0005Am-Kp for pgsql-bugs@lists.postgresql.org; Thu, 19 May 2022 04:14:17 +0000 Received: by mail-pl1-x636.google.com with SMTP id n8so3716325plh.1 for ; Wed, 18 May 2022 21:14:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=QM3AVc4rUGtWBGCZtuNk9hOnV/Sv4dqzMlkfzMkZ+po=; b=WXKafm6ejzrq6Sww6FWENL+7Fq88CnPVQ/gHHugzFVhFPG2b4NNWwyy7JvXsgkbjT5 62FW3qYH7mwL4N/Jfx6z1GT44cKzTf7d4HmBn8LLOQZGFiVKd+XoCjPzzVzY4gofFVIA nbxFM/GfWL0k7mKZm6DCDsGlp3kVZq5q09qWftJUVPqOAX55/bpxc9UXxtvZ8UwyuvtN 0gs2zbZXZ/y0GvKT5+Qpc41rtN0ylM2XESDL6hWdevamzVJjWPeyPbSEAEb5w9TJQ8rX mS+9RU5f6xRuwVaTtPD+8R+/8zseE9JQ74qD9en3iCpV6F7VOoQKtLsCupftDoaBIv2C dvTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=QM3AVc4rUGtWBGCZtuNk9hOnV/Sv4dqzMlkfzMkZ+po=; b=R4qwmt7MSC0nOCqozsdjoFMJLRS22oY2zhFyl8nyVm9iWmnVdpUVrE3+vsCfUspyFb 3NzSocYh6aSAhDEBmlrpGsb535HbsRaG7wqjv66YLZUdrs6SgROVEGQJ8qK6kW0SX6Ga KdBW7C6dXkykbtPufct5YULKdR5ScQdKdPVP2/Ax+QNNZXGcx+p12cVvWrhc6J8wS8V+ x/Vmrd6K5FL43s9oDPvW+GjAhVYF78qKvojgWJ3FmEevMWZr6svOlNbEMRfQKJld3NkV AoW+XphswRMws+28psBdNmUr/MQ1rJd2dzMY0W+pS5xuVsOOES5d/3jAIu8bv9h45av9 lf5w== X-Gm-Message-State: AOAM53126GaAFbwtYfR8tJM91PlRvmQjp+fLhkSPwDgzdQinmXRzAA5J lzyJ6Mc2LKnalHH3Y+ORvo8= X-Google-Smtp-Source: ABdhPJxBJpIpvI9lG8TnX+hdJRSfKiI84bhmlkhiacH0y2QNVq757YoLmefiUP8MO4IjRk5+6U71tQ== X-Received: by 2002:a17:902:d2c6:b0:161:6e0e:c5e1 with SMTP id n6-20020a170902d2c600b001616e0ec5e1mr2931685plc.139.1652933653655; Wed, 18 May 2022 21:14:13 -0700 (PDT) Received: from smtpclient.apple (ai126215211057.78.access-internet.ne.jp. [126.215.211.57]) by smtp.gmail.com with ESMTPSA id 64-20020a621643000000b0050dc762819asm2799976pfw.116.2022.05.18.21.14.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 18 May 2022 21:14:13 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-9B7ACE69-D68F-473C-85CD-F1607FF8AF50 Content-Transfer-Encoding: 7bit From: =?utf-8?B?6I+K5rGg56WQ?= Mime-Version: 1.0 (1.0) Subject: Re: About pg_basebackup Date: Thu, 19 May 2022 13:14:10 +0900 Message-Id: <87A19691-F8EE-4595-A974-DDC4FAFF88E8@gmail.com> References: Cc: PostgreSQL mailing lists In-Reply-To: To: "David G. Johnston" X-Mailer: iPhone Mail (19E258) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail-9B7ACE69-D68F-473C-85CD-F1607FF8AF50 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thank you for quick response. I=E2=80=99ll ask pgsql-general mailing list. Best regards, Yu > On May 19, 2022, at 12:46, David G. Johnston w= rote: >=20 > =EF=BB=BF >> On Wed, May 18, 2022 at 8:35 PM =E8=8F=8A=E6=B1=A0=E7=A5=90 wrote: >> Hi, >>=20 >> I executed the pg_basebackup command to set up a replication configuratio= n in postgresql, but the following message appears and replication didn=E2=80= =99t complete. >>=20 >> 2741/2742 tablespaces (/var/lib/pgsql/9.2/bac12609150596/12609150596 kB (= 100%), 2741/2742 tablespaces (/var/lib/pgsql/9.2/bac12609150596/12609150596 k= B (100%), 2742/2742 tablespaces NOTICE: pg_stop_backup cleanup done, waiting= for required WAL segments to be archived WARNING: pg_stop_backup still wait= ing for all required WAL segments to be archived (60 seconds elapsed) HINT: C= heck that your archive_command is executing properly. pg_stop_backup can be c= anceled safely, but the database backup will not be usable without all the W= AL segments. WARNING: pg_stop_backup still waiting for all required WAL segm= ents to be archived (120 seconds elapsed) =E3=83=BB =E3=83=BB =E3=83=BB >>=20 >> Please let me know how to deal with this. >>=20 >=20 > Impossible to say with the information provided. The PostgreSQL log file d= uring 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.= ..) >=20 > What specific version of the long unsupported version 9.2.x are you runnin= g? >=20 > This seems unlikely to be a bug. Support questions are more appropriately= directed to the pgsql-general mailing list. >=20 > David J. >=20 --Apple-Mail-9B7ACE69-D68F-473C-85CD-F1607FF8AF50 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thank you for quick response.
I=E2=80=99= ll ask pgsql= -general mailing list.

Be= st regards,
Yu<= br>

On May 19, 2022, at= 12:46, David G. Johnston <david.g.johnston@gmail.com> wrote:

<= /blockquote>
=EF=BB=BF
On Wed, May 18, 2022 at 8:35 PM =E8=8F=8A=E6=B1=A0=E7=A5=90 <y.kikuchi0714@gmail.com> wrote= :

Hi,

I ex= ecuted the pg_basebackup command to set up a replication configuration in po= stgresql, but the following message appears and replication didn=E2=80=99t c= omplete.

2741/2742 tablespaces (/var/lib/pgsql/9.2/bac12609150596/1260= 9150596 kB (100%), 2741/2742 tablespaces (/var/lib/pgsql/9.2/bac12609150596/= 12609150596 kB (100%), 2742/2742 tablespaces NOTICE: pg_stop_backup cleanup d= one, waiting for required WAL segments to be archived WARNING: pg_stop_backu= p still waiting for all required WAL segments to be archived (60 seconds ela= psed) HINT: Check that your archive_command is executing properly. pg_stop_b= ackup can be canceled safely, but the database backup will not be usable wit= hout all the WAL segments. WARNING: pg_stop_backup still waiting for all req= uired WAL segments to be archived (120 seconds elapsed) =E3=83=BB =E3=83=BB =E3= =83=BB

Please let me know how to deal with this.


Impossible to say with the information provided.&nbs= p; The PostgreSQL log file during this period should prove informative. = ; You have an archive_command set so look for any messages indicating it is f= ailing (just like the HINT says...)

What specific version o= f the long unsupported version 9.2.x are you running?

This= seems unlikely to be a bug.  Support questions are more appropriately d= irected to the pgsql-general mailing list.

David J.
=

= --Apple-Mail-9B7ACE69-D68F-473C-85CD-F1607FF8AF50--