Network Administrator <[EMAIL PROTECTED]> 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

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to