Re: pg_dump transaction's read-only mode

Gurjeet Singh <singh.gurjeet@gmail.com>

From: Gurjeet Singh <singh.gurjeet@gmail.com>
To: Pavan Deolasee <pavan.deolasee@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>, Kevin Grittner <Kevin.Grittner@wicourts.gov>, pgsql-hackers@postgresql.org
Date: 2013-01-16T14:04:27Z
Lists: pgsql-hackers
On Wed, Jan 16, 2013 at 1:21 AM, Pavan Deolasee <pavan.deolasee@gmail.com>wrote:

>
>
> On Wed, Jan 9, 2013 at 6:42 AM, Gurjeet Singh <singh.gurjeet@gmail.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 ?
>

Done.

-- 
Gurjeet Singh

http://gurjeet.singh.im/