Re: pg_dump transaction's read-only mode

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump transaction's read-only mode
Date: 2012-12-29 19:08:32
Message-ID: 20121229190832.GX16126@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Pavan Deolasee (pavan(dot)deolasee(at)gmail(dot)com) wrote:
> On Fri, Sep 7, 2012 at 6:06 PM, Kevin Grittner
> > 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 ?

This is on the next commitfest, so I figure it deserves some comment.
For my part- I tend to agree that we should have it always use a read
only transaction. Perhaps we should update the pg_dump documentation to
mention this as well though? Pavan, do you want to put together an
actual patch?

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2012-12-29 19:14:52 Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used
Previous Message Stephen Frost 2012-12-29 19:00:45 Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used