Re: [HACKERS] PG_UPGRADE status?
| От | Bruce Momjian |
|---|---|
| Тема | Re: [HACKERS] PG_UPGRADE status? |
| Дата | |
| Msg-id | 199909091626.MAA21308@candle.pha.pa.us обсуждение исходный текст |
| Ответ на | Re: [HACKERS] PG_UPGRADE status? (Lamar Owen <lamar.owen@wgcr.org>) |
| Список | pgsql-hackers |
> 2.) The first rpm's preinstall script starts running. The old version > of that rpm is still installed at this point, BUT I CAN'T EXECUTE ANY > DAEMONS -- the upgrade MIGHT be running in the wicked chroot environment > of the RedHat installer, with its restrictive set of commands. So, I > CANNOT start a postmaster, nor can I be assured that a postmaster is > running -- according to RedHat, since it could be running in the chroot > installer, I can't even run a ps to SEE if postmaster is running > (problems with a chrooted /proc...). Therefore, the preinstall script > CANNOT execute pg_dumpall. I can't even run a standalone backend -- > postmaster MIGHT be running.... And, I can't test to see if I'm running > in the installer or not... ;-( The only thing I CAN do is check /tmp for > the lock file. This seems almost impossible to handle. I have enough trouble wrinting PostgreSQL C code when I have total control over the environment. BTW, you can check for a running backend by trying to telnet to the 5432 port, or trying to do a connection to the unix domain socket. -- Bruce Momjian | http://www.op.net/~candle maillist@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 по дате отправления: