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-21 13:00:45 |
Message-ID: | 1323.1358773245@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:
> On Sun, Jan 20, 2013 at 4:29 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.
It supports servers back to 7.0. At some point we ought to consciously
desupport old servers and pull out the corresponding code, but that
needs to be an act of intention not omission ;-)
(It's entirely likely that the 7.0 server I keep around for testing this
is the last one in captivity anywhere. But IIRC, we've heard fairly
recent reports of people still using 7.2. We'd have to desupport before
7.3 to save any meaningful amount of pg_dump code, so I'm not convinced
it's time to pull the trigger on this quite yet.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2013-01-21 13:00:57 | Re: Making testing on Windows easier |
Previous Message | Noah Misch | 2013-01-21 12:55:44 | Re: Making testing on Windows easier |