On Wed, 2005-07-13 at 18:35 -0700, David Fetter wrote:
> I'm sure I'm not the first to bring up this way of doing pg_upgrade,
> but perhaps I can help seed a fruitful discussion on the matter.
> Ideally, these transformations would be both idempotent and
> reversible, although I understand that they may, by their nature, be
> neither.
I'm not sure it is easily possible to do all that you say as a general
rule. Each release will be different, so I think we need a person, not a
procedure. If we have a procedure, but no person, who will enforce the
procedure?
There is clearly an opening for an individual to track committed code
and to analyse what the upgrade actions would need to be for each. That
way, we might be able to implement things in a more upgrade friendly
manner (when we have a choice). We specialise in most other areas....
Changes to data format mostly will need an external program, since no
version of the server understands both formats.
Best Regards, Simon Riggs
