| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| 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-05 22:23:38 |
| Message-ID: | 200005052223.SAA05842@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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 ?
Great idea. We never had an automated way to do that before.
--
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 | Bruce Momjian | 2000-05-05 22:24:37 | Re: pg_group_name_index corrupt? |
| Previous Message | Olivier PRENANT | 2000-05-05 20:47:33 | Re: Porting reports (cont'd) |