On Mon, May 15, 2006 at 02:20:51PM -0500, Larry Rosenman wrote:
> > Yeah, but what's the ${command} ?
> >
> > If it's pg_ctl then all he's missing is the recent change to check
> > getppid. If it's execing postmaster directly then maybe we need
> > another theory.
>
> It's pg_ctl
>
> comman
Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
>> Except that the shell that's running su would be root, not pgsql, at
>> least in the case of FreeBSD. The guts of the current port's rc.d
>> file are:
>
>> su -l ${postgresql_user} -c "exec ${command} ${command_args}
>> ${rc_arg}"
>
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> Except that the shell that's running su would be root, not pgsql, at
> least in the case of FreeBSD. The guts of the current port's rc.d file
> are:
> su -l ${postgresql_user} -c "exec ${command} ${command_args} ${rc_arg}"
Yeah, but what's the ${comma
On Mon, May 15, 2006 at 09:23:33AM -0400, Tom Lane wrote:
> We've fixed this in recent releases by having the postmaster also check
> for a match to its parent process ID (getppid). The care in the start
> script comes because this only works for one level up. Therefore, you
> can't "su -c pg_ctl
Ruslan A Dautkhanov <[EMAIL PROTECTED]> writes:
> Server rebooted occasionally after power failure.
> And I have stale postmaster.pid file, so postmaster didn't start with error
> bill postgres[600]: [1-1] FATAL: file "postmaster.pid" already exists
You probably need a newer postgres version
Hello !
Server rebooted occasionally after power failure.
And I have stale postmaster.pid file, so postmaster didn't start with error
bill postgres[600]: [1-1] FATAL: file "postmaster.pid" already exists
I think startup script and/or pg_ctl have to be written to check if that
process really
