| From: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> |
|---|---|
| To: | Pavan Deolasee <pavan(dot)deolasee(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 14:04:27 |
| Message-ID: | CABwTF4WUJO51kg_32Sg0S-VahcTO0Fhc91=u8+05j06mzy1a3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 16, 2013 at 1:21 AM, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>wrote:
>
>
> 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 ?
>
Done.
--
Gurjeet Singh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-01-16 14:05:39 | Re: Parallel query execution |
| Previous Message | Stephen Frost | 2013-01-16 14:02:45 | Re: CF3+4 (was Re: Parallel query execution) |