RE: pg_group_name_index corrupt? - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject RE: pg_group_name_index corrupt?
Date
Msg-id NDBBIJLOILGIKBGDINDFMENFCEAA.Inoue@tpf.co.jp
Whole thread Raw
In response to Re: pg_group_name_index corrupt?  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> 
> > If I remember correctly,pg_upgrade doesn't shutdown the postmaster
> > after(or before) moving OLD data to the target dir though it tells us
> > the message "You must stop/start the postmaster ...".
> > How about calling pg_ctl from pg_upgrade to stop the postmaster ?
> 
> Added to TODO list.
>

Hmm,what I meant is to simply insert a command call 'pg_ctl -w stop'
before moving old data to the target directory in pg_upgrade.
It seems dangerous to leave the postmaster alive that doesn't
know the changes on empty tables created by pg_upgrade.

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ROLLBACK of DROP TABLE leaves database in inconsistent state
Next
From: The Hermit Hacker
Date:
Subject: Re: Passwords