Re: pg_dump transaction's read-only mode

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump transaction's read-only mode
Date: 2012-09-10 16:30:05
Message-ID: CABOikdNFuZho1EfJZdyeaUdwQTc2DhfiTf836c=QEaAavszMRw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 7, 2012 at 6:06 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-09-10 16:50:11 Re: Proof of concept: standalone backend with full FE/BE protocol
Previous Message Gurjeet Singh 2012-09-10 16:25:00 Re: Proof of concept: standalone backend with full FE/BE protocol