From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org, The Hermit Hacker <scrappy(at)hub(dot)org> |
Subject: | Re: pg_group_name_index corrupt? |
Date: | 2000-05-05 22:47:44 |
Message-ID: | 200005052247.SAA07302@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> How about calling pg_ctl from pg_upgrade to stop the postmaster ?
>
> > Great idea. We never had an automated way to do that before.
>
> I'd just as soon *not* have pg_upgrade assuming that it knows how
> I like my postmaster started. If pg_ctl will work to stop a postmaster
> whether or not it was started with pg_ctl, then it'd probably be a good
> idea to use pg_ctl to ensure that there is no postmaster running in the
> target database. I'd suggest not trying to restart the postmaster
> automatically afterwards, though. Too much site dependency in that.
But doesn't it find the params from the last startup?
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-05-05 22:50:39 | Re: Porting reports (cont'd) |
Previous Message | Sverre H. Huseby | 2000-05-05 22:40:24 | You're on SecurityFocus.com for the cleartext passwords. |