Re: pg_dump transaction's read-only mode

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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: 2013-01-19 22:59:32
Message-ID: 3093.1358636372@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.) I fixed that
and committed it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2013-01-19 23:15:39 Re: Strange Windows problem, lock_timeout test request
Previous Message Jeff Janes 2013-01-19 22:58:32 Re: lazy_vacuum_heap()'s removal of HEAPTUPLE_DEAD tuples