X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 5E7D99DC86A for ; Mon, 9 Jan 2006 14:00:10 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 38201-08 for ; Mon, 9 Jan 2006 14:00:09 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.201]) by postgresql.org (Postfix) with ESMTP id B013E9DC814 for ; Mon, 9 Jan 2006 14:00:07 -0400 (AST) Received: by xproxy.gmail.com with SMTP id s14so2562252wxc for ; Mon, 09 Jan 2006 10:00:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=lypDse/jAyOdg7tJ/gHzFoPpkZypfgrJBnIPKQE1AHG6xBFnzwwBNtsDZ61unCkdG88NMpx2a/Urfr4/CJTBrvL/V8HSfUWODidf6I0rFiHbsZuwZnmB2NrCXf4c4G4f+1sZqZu3gxpufjToq28Qv3VGOesXcXj8nSruIxp52v0= Received: by 10.70.132.4 with SMTP id f4mr5428346wxd; Mon, 09 Jan 2006 10:00:07 -0800 (PST) Received: by 10.70.84.7 with HTTP; Mon, 9 Jan 2006 10:00:07 -0800 (PST) Message-ID: <1d219a6f0601091000u45439e1dq1eb8296e8ffa3dba@mail.gmail.com> Date: Mon, 9 Jan 2006 13:00:07 -0500 From: Chris Hoover To: Michael Fuhr Subject: Re: What happens to transactions durring a pg_dump? Cc: "pgsql-admin@postgresql.org" In-Reply-To: <20060109174511.GA43775@winnie.fuhr.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_83437_3239064.1136829607813" References: <1d219a6f0601090922s5224e78emd68cf850b836c2af@mail.gmail.com> <20060109174511.GA43775@winnie.fuhr.org> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.101 required=5 tests=[AWL=0.100, HTML_MESSAGE=0.001] X-Spam-Score: 0.101 X-Spam-Level: X-Archive-Number: 200601/94 X-Sequence-Number: 20182 ------=_Part_83437_3239064.1136829607813 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 1/9/06, Michael Fuhr wrote: > > On Mon, Jan 09, 2006 at 12:22:27PM -0500, Chris Hoover wrote: > > I'm trying to understand better what happens to a transaction that is > > commited in the middle of a pg_dump. Is the transaction included in th= e > > database dump, or is it excluded. > > If you look at the pg_dump source code or turn on query logging, > you should see that pg_dump starts with > > BEGIN > SET TRANSACTION ISOLATION LEVEL SERIALIZABLE > > See "Transaction Isolation" in the "Concurrency Control" chapter of the > documentation for an explanation of what that means. > > http://www.postgresql.org/docs/8.1/interactive/transaction-iso.html > > -- > Michael Fuhr > Just to make sure I correctly understood what I read, once pg_dump issues the : BEGIN SET TRANSACTION ISOLATION LEVEL SERIALIZABLE The backup will only see transactions that were commited before the isolation level was set Is this correct? Any transactions that are commite= d while the backup is running are not seen by pg_dump. Correct? Thanks, Chris ------=_Part_83437_3239064.1136829607813 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline


Just to make sure I correctly understood what I read, once pg_dump issues t= he :
BEGIN
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE

The backup will only see transactions that were commited before the isolation level was set Is this correct?  Any transactions that are commited while the backup is running are not seen by pg_dump.

Correct?

Thanks,

Chris
------=_Part_83437_3239064.1136829607813--