| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kinsey, Ben" <BenK(at)aiinet(dot)com> |
| Cc: | Giles Lean <giles(at)nemeton(dot)com(dot)au>, sk9887(at)sbc(dot)com, pgsql-bugs(at)postgresql(dot)org, "Wahl, Steven" <stevenwa(at)aiinet(dot)com> |
| Subject: | Re: Bug #882: Cannot manually log in to database. |
| Date: | 2003-01-24 16:55:35 |
| Message-ID: | 14007.1043427335@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Kinsey, Ben" <BenK(at)aiinet(dot)com> writes:
> Here's a little more detail as to how this socket file was getting deleted:
> On the system I'm using, if you attempt to start postmaster when an instance
> of it is already running, the socket file gets deleted. It was discovered
> that upon bootup of the system, the postgres startup script was being
> executed twice in the /sbin/rc3.d directory, and this was causing the socket
> file to get deleted. It wasn't a cron job.
The second postmaster launch was doing that? It should not, because it
should detect that there's already a postmaster before it starts messing
with the socket file. Perhaps there's a gratuitous "rm" of the socket
file or the socket lockfile in the startup script?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql-bugs | 2003-01-24 17:37:06 | Bug #884: Schema access not inherited by functions declared SECURITY DEFINER |
| Previous Message | Kinsey, Ben | 2003-01-24 16:14:23 | Re: Bug #882: Cannot manually log in to database. |