On 01/21/2013 02:00 PM, Tom Lane wrote: > Pavan Deolasee <pavan.deola...@gmail.com> writes: >> On Sun, Jan 20, 2013 at 4:29 AM, Tom Lane <t...@sss.pgh.pa.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.)
old versions are still alive - just yesterday we had someone on IRC trying to build 7.1.3 on a modern ubuntu installation because he has an old app depending on it., and especially 7.2 shows up regulary as well. If the effort to keep pg_dump support for those alive is not too bad, we should try to support them as long as we can. Stefan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
