| From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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: | 2013-01-21 05:59:40 |
| Message-ID: | CABOikdPjsMaoUb-vqThJiowjfOXd9EZ3Z8O6R-bpUUz1JphjbQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jan 20, 2013 at 4:29 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> writes:
>> Sorry for posting on such an old thread. But here is a patch that
>> fixes this. I'm also adding to the next commitfest so that we don't
>> lose track of it again.
>
> As submitted, this broke pg_dump for dumping from pre-8.0 servers.
> (7.4 didn't accept commas in SET TRANSACTION syntax, and versions
> before that didn't have the READ ONLY option at all.)
My bad. I did not realize that pg_dump is still supported for pre-8.0 releases.
> I fixed that
> and committed it.
>
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vivek Singh Raghuwanshi | 2013-01-21 06:03:54 | Re: [HACKERS] Error Building rpm |
| Previous Message | Pavan Deolasee | 2013-01-21 05:57:12 | Re: Removing PD_ALL_VISIBLE |