Re: server auto-restarts and ipcs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)MIT(dot)EDU>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: server auto-restarts and ipcs
Date: 2004-11-09 21:36:17
Message-ID: 5353.1100036177@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Greg Stark <gsstark(at)MIT(dot)EDU> writes:
> Oh I missed the fact that you were talking about after a reboot. So the
> algorithm I described would produce exactly the same sequence of ids after any
> reboot given the same sequence of creation and deletions. Even if there's a
> different sequence as long as the n'th creation is for the m'th array slot it
> would get the same id. So collisions would be very common.

This seems to square with Ed's complaint that he frequently sees a
collision after a reboot. I've just committed some code that makes a
more extensive check as to whether a pre-existing segment actually has
any relevance to our data directory; should fix the problem.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message ru.igarashi 2004-11-09 21:37:43 Re: Important Info on comp.databases.postgresql.general
Previous Message Robert Treat 2004-11-09 21:13:41 Re: [GENERAL] FTP mirror problems

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-11-09 22:27:14 A modest proposal: get rid of GUC's USERLIMIT variable category
Previous Message Greg Stark 2004-11-09 20:52:39 Re: server auto-restarts and ipcs