RE: pg_group_name_index corrupt?

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>, "The Hermit Hacker" <scrappy(at)hub(dot)org>
Subject: RE: pg_group_name_index corrupt?
Date: 2000-05-06 23:50:16
Message-ID: NDBBIJLOILGIKBGDINDFMENFCEAA.Inoue@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)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(at)tpf(dot)co(dot)jp

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2000-05-07 01:54:37 Re: Passwords
Previous Message Tom Lane 2000-05-06 22:21:19 Re: ROLLBACK of DROP TABLE leaves database in inconsistent state