Re: pg_group_name_index corrupt?
От | Bruce Momjian |
---|---|
Тема | Re: pg_group_name_index corrupt? |
Дата | |
Msg-id | 200005052247.SAA07302@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: pg_group_name_index corrupt? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pg_group_name_index corrupt?
|
Список | pgsql-hackers |
> Bruce Momjian <pgman@candle.pha.pa.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@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
В списке pgsql-hackers по дате отправления: