Re: [HACKERS] PG_UPGRADE status?

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] PG_UPGRADE status?
Date: 1999-09-09 16:26:15
Message-ID: 199909091626.MAA21308@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-09-09 16:36:59 Re: [HACKERS] Vacuum analyze bug CAUGHT
Previous Message Bruce Momjian 1999-09-09 16:20:28 Re: [HACKERS] PG_UPGRADE status