From: | "Stupor Genius" <stuporg(at)erols(dot)com> |
---|---|
To: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: [HACKERS] Lots 'o patches |
Date: | 1998-06-02 00:44:23 |
Message-ID: | 001001bd8dbf$964de840$4299accf@darren |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> 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
seems?
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.
darrenk
From | Date | Subject | |
---|---|---|---|
Next Message | t-ishii | 1998-06-02 00:52:18 | Re: [HACKERS] duplicate oids in pg_proc |
Previous Message | The Hermit Hacker | 1998-06-02 00:31:42 | Re: [HACKERS] custom types and optimization |