| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
| Cc: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Could postgres be much cleaner if a future release skipped backward compatibility? |
| Date: | 2009-10-20 02:01:48 |
| Message-ID: | 16570.1256004108@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Marc G. Fournier" <scrappy(at)hub(dot)org> writes:
> Just curious, but with that thought in mind, are we doing any code
> cleanups as far as EOL releases? Ie. is there any code in our tree right
> now that is for 'backward compatibility' for 7.3.x versions that could be
> cleaned out?
Well, we were just trying to pull out add_missing_from, and look how far
that's gotten ...
Something that has been suggested is to rip out pg_dump's support for
pre-7.3 servers, which would probably be easier to get through because
it wouldn't create any user-visible feature loss. It wouldn't be a
monstrous savings but it'd certainly simplify matters somewhat.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira de Oliveira | 2009-10-20 02:11:58 | Add a pgstat config column to pg_database, so this, entire thing can be enabled/disabled on a per db basis |
| Previous Message | Marc G. Fournier | 2009-10-20 01:55:47 | Re: Could postgres be much cleaner if a future release skipped backward compatibility? |