| From: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Josh Berkus" <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [CORE] RC1 blocker issues |
| Date: | 2006-11-28 11:44:19 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA579018FE15F@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-11-28 11:55:11 | Re: Where is detab? |
| Previous Message | Peter Eisentraut | 2006-11-28 11:43:58 | Where is detab? |