| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Alexandru Cârstoiu <alexandru(dot)carstoiu(at)excelsarc(dot)ro>, pgsql-hackers(at)postgresql(dot)org, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Subject: | Re: PG 7.3 is five years old today |
| Date: | 2007-11-28 15:11:37 |
| Message-ID: | 29790.1196262697@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> Whether there's any need to support the old protocol in the server depends on
> whether there are any clients out there which use it which is harder to
> determine and not affected by whether Postgres 7.3 is still around.
Right. There's really not much to be gained by dropping it on the
server side anyway. libpq might possibly be simplified by a useful
amount, but on the other hand we probably want to keep its current
structure for the inevitable v4 protocol.
Another area where we might think about dropping some stuff is pg_dump.
If we got rid of the requirement to support dumps from pre-7.3 servers
then it could assume server-side dependencies exist, and lose all the
code for trying to behave sanely without 'em.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2007-11-28 15:12:58 | Re: pgwin32_open returning EINVAL |
| Previous Message | sulfinu | 2007-11-28 15:07:08 | Re: PG 7.3 is five years old today |