| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Justin Clift <justin(at)postgresql(dot)org> |
| Cc: | greg(at)turnstep(dot)com, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: v7.3.1 psql against a v7.2.x database ... |
| Date: | 2003-01-18 05:52:10 |
| Message-ID: | 20030118135025.E3621-100000@houston.familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> With ever more larger businesses adopting PostgreSQL, and that leading
> on to more places having several versions of PostgreSQL in operation
> simultaneously (i.e. development vs production) we're probably going to
> need to give psql the ability to handle whichever version of the PG
> backend it happens to connect to.
>
> Marc's suggestion of breaking psql into it's own sub-project makes good
> sense from that point of view.
Subproject or not, why don't we just rearrange psql to dynamically load a
library of functions, eg:
libpsql72.so
libpsql73.so
etc...
And in them you have functions like:
printTableDef();
printViewDef();
etc...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2003-01-18 06:41:09 | Re: Can we revisit the thought of PostgreSQL 7.2.4? |
| Previous Message | Bruce Momjian | 2003-01-18 05:16:00 | Re: Can we revisit the thought of PostgreSQL 7.2.4? |