pg_ctl problem (was Re: BeOS Patch)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Cyril VELTER <cyril(dot)velter(at)libertysurf(dot)fr>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgreSQL(dot)org
Subject: pg_ctl problem (was Re: BeOS Patch)
Date: 2001-03-18 17:11:54
Message-ID: 19992.984935514@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Cyril VELTER <cyril(dot)velter(at)libertysurf(dot)fr> writes:
> pg_ctl output when no shm segments left

> pg_ctl: It seems another postmaster is running. Trying to start postmaster
> anyway.
> pg_ctl: cannot start postmaster <-------- not true !!!
> Examine the log output.
> DEBUG: database system was interrupted at 2001-03-18 12:01:57 CET
> DEBUG: CheckPoint record at (0, 20204684)
> DEBUG: Redo record at (0, 20204684); Undo record at (0, 0); Shutdown TRUE
> DEBUG: NextTransactionId: 5384; NextOid: 153313
> DEBUG: database system was not properly shut down; automatic recovery in
> progress...
> DEBUG: ReadRecord: record with zero len at (0, 20204748)
> DEBUG: redo is not required
> DEBUG: database system is in production state

Looking at the pg_ctl script, it seems this must be coming from

eval '$po_path' '$POSTOPTS' $logopt '&'

if [ -f $PIDFILE ];then
if [ "`sed -n 1p $PIDFILE`" = "$pid" ];then
echo "$CMDNAME: cannot start postmaster" 1>&2
echo "Examine the log output." 1>&2
exit 1
fi
fi

which is clearly not giving the postmaster enough time to remove or
rewrite the pidfile. Shouldn't we put a "sleep 1" in there before
the "if"?

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-03-18 17:29:21 Re: pg_ctl problem (was Re: BeOS Patch)
Previous Message Alexander Klimov 2001-03-18 16:40:32 Re: problems with startup script on upgrade