Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hkV2y-0004Ez-Iw for pgsql-admin@arkaria.postgresql.org; Mon, 08 Jul 2019 14:55:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hkV2w-0001QM-9O for pgsql-admin@arkaria.postgresql.org; Mon, 08 Jul 2019 14:55:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hkV2v-0001QF-TD for pgsql-admin@lists.postgresql.org; Mon, 08 Jul 2019 14:55:14 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hkV0F-00014g-TP for pgsql-admin@postgresql.org; Mon, 08 Jul 2019 14:52:33 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 719ED5F7B5; Mon, 8 Jul 2019 10:52:26 -0400 (EDT) Date: Mon, 8 Jul 2019 10:52:26 -0400 From: Stephen Frost To: Thorsten =?iso-8859-1?Q?Sch=F6ning?= Cc: pgsql-admin@postgresql.org Subject: Re: Does pg_start_backup changes how Postgres writes data? Message-ID: <20190708145226.GZ29202@tamriel.snowman.net> References: <171339952.20190708105025@am-soft.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="A1Iwnsx6rNfRhs6P" Content-Disposition: inline In-Reply-To: <171339952.20190708105025@am-soft.de> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --A1Iwnsx6rNfRhs6P Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Thorsten Sch=F6ning (tschoening@am-soft.de) wrote: > From what I understand from reading the docs and multiple other > sources, I have a different opinion: The only thing pg_start_backup > changes regarding writes in the data directory of Postgres is that a > checkpoint is done as part of starting the backup, even if no > checkpoint would be needed currently otherwise. After that is done, Magnus' already replied to most of this, but I wanted to point out that you can control if pg_start_backup forces an immediate checkpoint or if it waits for the checkpoint to complete naturally. Thanks, Stephen --A1Iwnsx6rNfRhs6P Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJdI1iqAAoJEO1sijiDR2RVtQkP/2Jks2jqfuvC2m/UEfRxGxx2 fv8R46MYvsuEud/xaufu4F+jwuUqxKLQMOWujtrweeN8EPHXZGU5xqQN3aLsH61r 4rkDux5qdqb+fneHOCwMP9yG0J2yo+z4VNnu9N2frZNCAl/8bASwNqBDmjUFOH5V 3JJegKGR3BCz2VyHHFTsX7NIUu250NynvXt2zOWz+k/DbU91vc7dKB0NRhqocMbs ZMJ+R/6KpY3fxxiAcb8b0bUpq9nWPDAGCWotmchQhl1naCHGIC6ADVORaKrra0pI ZyYPoV0Q2UMadk//l/VcollRBq/FvMNSfwb3iGp1qcG60g/33U7iENRMCxbtI2kN z54AE+ywKRtf5lShzwm2I19fSw4wFjibU5iUTtdopfTZSYu848Hm1e69MaFFDl4d FNZizEMXyOJuamaTp2kcXlaOpbAUaDcotqid9VZz444mfbvJH/5EoJCVvE4qE9pM /uN2FxLa4E/YceusKLeo0DeteMdTbak0vxqQWKqn6CUrsrsI61IYySjt3O99U0JX 6xvT+vHIPHdu/ygBK+F6BdeqAoCJVQLqEQNVlju0cfjtuAhrptMtP5pdvSeMDqR0 gz6mB7heMILLKBhzd2zvWE58ZoEW7lexDKcgkmd/my0buAAN8ov0uKiocrnEr7Gs +neSGDcqL6/l8xq+ltHl =MOAh -----END PGP SIGNATURE----- --A1Iwnsx6rNfRhs6P--