On Sun, 2003-09-14 at 23:08, Tom Lane wrote:
> 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.
I think that every effort should be made so that the on-disk struct-
ure (ODS) doesn't have to change when tablespaces is implemented.
I.e., oid-based files live side-by-side with tablespaces.
At a minimum, it should be "ok, you don't *have* to do a dump/restore
to migrate to v7.7, but if you want the tablespaces that are brand
new in v7.7, you must dump data, and recreate the schema with table-
spaces before restoring".
--
-----------------------------------------------------------------
Ron Johnson, Jr. [EMAIL PROTECTED]
Jefferson, LA USA
"(Women are) like compilers. They take simple statements and
make them into big productions."
Pitr Dubovitch
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
