Re: [CORE] RC1 blocker issues - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: [CORE] RC1 blocker issues
Date
Msg-id E1539E0ED7043848906A8FF995BDA579018FE15F@m0143.s-mxs.net
Whole thread Raw
In response to Re: [CORE] RC1 blocker issues  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: [CORE] RC1 blocker issues  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
> "SELECT *".  It's unfortunate that we have to go through another
initdb
> / pg_dump on these, but I understand the arguments for the change, and
> we did know it was still beta when we decided to go that way.

You can certainly find a workaround to not need an initdb.
drop indexes based on the changed to_char function,
verify other incompatible changes since beta3 ?? anybody think of
something else ?
shutdown the db,
binary edit the new version into pg_control,
start db with new version,
recreate the changed system view,
recreate indexes dropped above.

It is just that this is not automated. But if we make a list of the
initdb forcing
changes, it should be possible.

Andreas


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Where is detab?
Next
From: Alvaro Herrera
Date:
Subject: Re: Where is detab?