From: Stupor Genius <stuporg@erols.com>
To: Hackers <pgsql-hackers@postgresql.org>
Subject: RE: [HACKERS] Lots 'o patches
Date: Mon, 1 Jun 1998 20:44:23 -0400
Message-ID: <001001bd8dbf$964de840$4299accf@darren> (raw)
In-Reply-To: <199806011424.KAA08421@candle.pha.pa.us>
>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: stuporg@erols.com
Subject: RE: [HACKERS] Lots 'o patches
In-Reply-To: <001001bd8dbf$964de840$4299accf@darren>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox