RE: [HACKERS] Lots 'o patches - Mailing list pgsql-hackers

From Stupor Genius
Subject RE: [HACKERS] Lots 'o patches
Date
Msg-id 001001bd8dbf$964de840$4299accf@darren
Whole thread Raw
In response to Re: [HACKERS] Lots 'o patches  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] Lots 'o patches  (dg@illustra.com (David Gould))
List 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


pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] custom types and optimization
Next
From: t-ishii@sra.co.jp
Date:
Subject: Re: [HACKERS] duplicate oids in pg_proc