Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_dump transaction's read-only mode - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: pg_dump transaction's read-only mode
Date
Msg-id CABOikdNFuZho1EfJZdyeaUdwQTc2DhfiTf836c=QEaAavszMRw@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump transaction's read-only mode  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: pg_dump transaction's read-only mode  (Pavan Deolasee <pavan.deolasee@gmail.com>)
Re: pg_dump transaction's read-only mode  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Tree view 
On Fri, Sep 7, 2012 at 6:06 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:


> That makes sense to me.  The reason I didn't make that change when I
> added the serializable special case to pg_dump was that it seemed
> like a separate question; I didn't want to complicate an already big
> patch with unnecessary changes to non-serializable transactions.
>

If we agree, should we change that now ?

Thanks,
Pavan

pgsql-hackers by date:

Previous
From: Gurjeet Singh
Date:
Subject: Re: Proof of concept: standalone backend with full FE/BE protocol
Next
From: Tom Lane
Date:
Subject: Re: Proof of concept: standalone backend with full FE/BE protocol