| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "Bogus data in lock file" shouldn't be FATAL? |
| Date: | 2010-08-16 15:59:44 |
| Message-ID: | 1281973704-sup-2598@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Tom Lane's message of lun ago 16 11:18:32 -0400 2010:
> We could perhaps address that risk another way: after having written
> postmaster.pid, try to read it back to verify that it contains what we
> wrote, and abort if not. Then, if we can't read it during startup,
> it's okay to assume there is no conflicting postmaster.
Makes sense.
BTW some past evidence:
http://archives.postgresql.org/message-id/e3e180dc0905070719q58136caai23fbb777fd3c0df7@mail.gmail.com
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-08-16 16:00:44 | Re: "Bogus data in lock file" shouldn't be FATAL? |
| Previous Message | Joshua D. Drake | 2010-08-16 15:53:06 | Re: Git migration timeline |