| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Network Administrator <netadmin(at)vcsn(dot)com> |
| Cc: | PgSQL General ML <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: State of Beta 2 |
| Date: | 2003-09-15 04:08:21 |
| Message-ID: | 3169.1063598901@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Network Administrator <netadmin(at)vcsn(dot)com> writes:
> ... However it seems to me that right now that this might not be
> possible while the backend is changing between major releases.
> Perhaps once that doesn't fluxate as much it might be feasible to
> create these layer so that it is not too fat.
Yeah, that's been in the back of my mind also. Once we have tablespaces
and a couple of the other basic features we're still missing, it might
be a more reasonable proposition to freeze the on-disk representation.
At the very least we could quantize it a little more --- say, group
changes that affect user table representation into every third or fourth
release.
But until we have a production-quality "pg_upgrade" this is all moot.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Gearon | 2003-09-15 06:52:40 | Re: case-insensitive database |
| Previous Message | elein | 2003-09-15 03:57:55 | [elein@varlena.com: Re: is General Bits Issue # 43 correct?] |