| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>, "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 16:02:21 |
| Message-ID: | 456C092C.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> On Tue, Nov 28, 2006 at 5:44 AM, in message
<E1539E0ED7043848906A8FF995BDA579018FE15F(at)m0143(dot)s-mxs(dot)net>,
"Zeugswetter
Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> wrote:
>> "SELECT *". It's unfortunate that we have to go through another
>> initdb
>
> You can certainly find a workaround to not need an initdb.
That would save some time.
> drop indexes based on the changed to_char function,
There are none.
> verify other incompatible changes since beta3 ?? anybody think of
> something else ?
Anybody?
> shutdown the db,
> binary edit the new version into pg_control,
Anything besides offset 000C to 000F?
> start db with new version,
> recreate the changed system view,
Are these all of them?:
pg_stat_all_tables
pg_stat_sys_tables
pg_stat_user_tables
Any special tricks to replacing these in a database that's been in
use?
Thanks,
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-11-28 16:02:42 | Re: Short writes |
| Previous Message | Chris Browne | 2006-11-28 15:59:23 | Re: FAQs and Port Status |