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 A5AC69DC809 for ; Mon, 9 Jan 2006 13:45:22 -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 38763-03 for ; Mon, 9 Jan 2006 13:45:21 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by postgresql.org (Postfix) with ESMTP id DEC759DC896 for ; Mon, 9 Jan 2006 13:45:17 -0400 (AST) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id k09HjCbB005938 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 10:45:14 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.4/8.13.4) with ESMTP id k09HjBQ1050092; Mon, 9 Jan 2006 10:45:11 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.4/8.13.4/Submit) id k09HjB5q050091; Mon, 9 Jan 2006 10:45:11 -0700 (MST) (envelope-from mfuhr) Date: Mon, 9 Jan 2006 10:45:11 -0700 From: Michael Fuhr To: Chris Hoover Cc: "pgsql-admin@postgresql.org" Subject: Re: What happens to transactions durring a pg_dump? Message-ID: <20060109174511.GA43775@winnie.fuhr.org> References: <1d219a6f0601090922s5224e78emd68cf850b836c2af@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1d219a6f0601090922s5224e78emd68cf850b836c2af@mail.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.082 required=5 tests=[AWL=0.082] X-Spam-Score: 0.082 X-Spam-Level: X-Archive-Number: 200601/93 X-Sequence-Number: 20181 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 the > 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