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 CABOikdM2WZcHj-+eia32fWdQqgybYWi-fNKBJUsma5_XOFZDww@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump transaction's read-only mode  (Pavan Deolasee <pavan.deolasee@gmail.com>)
Responses Re: pg_dump transaction's read-only mode
List pgsql-hackers
On Mon, Sep 10, 2012 at 10:00 PM, Pavan Deolasee
<pavan.deolasee@gmail.com> wrote:
> 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 ?
>

Sorry for posting on such an old thread. But here is a patch that
fixes this. I'm also adding to the next commitfest so that we don't
lose track of it again.

Thanks,
Pavan

--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee

Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: WIP patch for hint bit i/o mitigation
Next
From: Amit Kapila
Date:
Subject: Re: [BUG?] lag of minRecoveryPont in archive recovery