Skip site navigation (1) Skip section navigation (2)

Re: pg_dump transaction's read-only mode

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, 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: 2013-01-16 06:21:32
Message-ID: CABOikdM3vjJt+gR4XEG7qPUQUSk_r=8WQoWf21OBEA_Rbe192w@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Jan 9, 2013 at 6:42 AM, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>wrote:

>
>>
> I have updated the commitfest submission to link to the correct patch
> email.
>
>
Thanks Gurjeet.


> I initially thought that this patch deserves accompanying documentation
> because pg_dump's serializable transaction may error out because of a
> conflict. But the following line in the docs [1] confirms otherwise:
>
> "read-only transactions will never have serialization conflicts"
>
> So no doc patch necessary :)
>
>
Can you please mark the patch as "Ready for committer" if you think that
way ?

Thanks,
Pavan

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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2013-01-16 06:28:09
Subject: Re: Curious buildfarm failures (fwd)
Previous:From: Kevin GrittnerDate: 2013-01-16 05:40:55
Subject: Re: Materialized views WIP patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group