> That is going to be difficult to do. We used to have some SQL scripts
> that could make the required database changes, but when system table
> structure changes, I can't imagine how we would migrate that without a
> dump/reload. I suppose we could keep the data/index files with user data,
> run initdb, and move the data files back, but we need the system table
> info reloaded into the new system tables.
If the tuple header info doesn't change, this doesn't seem that tough.
Just do a dump the pg_* tables and reload them. The system tables are
"small" compared to the size of user data/indexes, no?
Or is there some extremely obvious reason that this is harder than it
But then again, what are the odds that changes for a release will only
affect system tables so not to require a data dump? Not good I'd say.
In response to
pgsql-hackers by date
|Next:||From: t-ishii||Date: 1998-06-02 00:52:18|
|Subject: Re: [HACKERS] duplicate oids in pg_proc |
|Previous:||From: The Hermit Hacker||Date: 1998-06-02 00:31:42|
|Subject: Re: [HACKERS] custom types and optimization|