Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1vlCAs-008lTn-0s
	for pgsql-general@arkaria.postgresql.org;
	Wed, 28 Jan 2026 20:30:02 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1vlCAr-003Zkc-1L
	for pgsql-general@arkaria.postgresql.org;
	Wed, 28 Jan 2026 20:30:01 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <xof@thebuild.com>)
	id 1vlCAr-003ZkO-08
	for pgsql-general@lists.postgresql.org;
	Wed, 28 Jan 2026 20:30:01 +0000
Received: from smtp94.ord1d.emailsrvr.com ([184.106.54.94])
	by makus.postgresql.org with esmtps  (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <xof@thebuild.com>)
	id 1vlCAo-002nPh-24
	for pgsql-general@lists.postgresql.org;
	Wed, 28 Jan 2026 20:30:00 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=g001.emailsrvr.com;
	s=feedback; t=1769632198;
	bh=XYR52aEzubwLKju7Hdfb3GqLLqdykoXvIMZDNtrbqDk=;
	h=Subject:From:Date:To:From;
	b=iDaJW459IPwknixET9q3/EWDeALc+8+Jfyl5T+bzWuN06wZWRrUoG/u9CCjOUy0Hn
	 xH3cGPloborkbyg+uyZa+ANh9+5kDhw+D7B0uXBiHbsKKzbvB4wzx2MMaY3xGUNXl5
	 nsmRJMmwOlQ+1VioOBzkrgp4dBZe0mIxwSN0VbGQ=
X-Auth-ID: xof@thebuild.com
Received: by smtp4.relay.ord1d.emailsrvr.com (Authenticated sender: xof-AT-thebuild.com) with ESMTPSA id 8A21A401A7;
	Wed, 28 Jan 2026 15:29:58 -0500 (EST)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.8\))
Subject: Re: About backups
From: Christophe Pettus <xof@thebuild.com>
In-Reply-To: <259609552.3013229.1769632103875@mail.yahoo.com>
Date: Wed, 28 Jan 2026 12:29:57 -0800
Cc: pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC52E7A1-6ADE-4711-990F-8CCA1E34FE0A@thebuild.com>
References: <1730736265.4259921.1769443263077.ref@mail.yahoo.com>
 <1730736265.4259921.1769443263077@mail.yahoo.com>
 <f88a803f-2954-44c5-bd29-e7f1dc5f9d02@aklaver.com>
 <2097370962.4296686.1769449473672@mail.yahoo.com>
 <5efd76b75e527a6558dd69ba4364699f256a813a.camel@tpg.com.au>
 <259609552.3013229.1769632103875@mail.yahoo.com>
To: felix.quintgz@yahoo.com
X-Mailer: Apple Mail (2.3776.700.51.11.8)
X-Classification-ID: 9e8c55b2-c5de-4186-a1ce-c0aa96a7e642-1-1
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/EC52E7A1-6ADE-4711-990F-8CCA1E34FE0A%40thebuild.com>
Precedence: bulk



> On Jan 28, 2026, at 12:28, felix.quintgz@yahoo.com wrote:
>=20
> What happens if I start a backup in the middle of a user transaction?=20=

> The transaction can end before or after the backup ends, and it can =
also start before or after the backup begins.

pg_dump takes a snapshot at the start of the dump, so the dump is =
consistent at a transaction boundary.  Of course, only transactions that =
have already committed at the time of the snapshot will appear in the =
dump.=