Postgres Pro
Downloads
Home   >   mailing lists

pgsql: Put a CHECK_FOR_INTERRUPTS call into the loops that try to find a - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Put a CHECK_FOR_INTERRUPTS call into the loops that try to find a
Date
Msg-id 20080220174409.767DD754108@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Tree view 
Log Message:
-----------
Put a CHECK_FOR_INTERRUPTS call into the loops that try to find a unique new
OID or new relfilenode.  If the existing OIDs are sufficiently densely
populated, this could take a long time (perhaps even be an infinite loop),
so it seems wise to allow the system to respond to a cancel interrupt here.
Per a gripe from Jacky Leng.

Backpatch as far as 8.1.  Older versions just fail on OID collision,
instead of looping.

Modified Files:
--------------
    pgsql/src/backend/catalog:
        catalog.c (r1.72 -> r1.73)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/catalog.c?r1=1.72&r2=1.73)

pgsql-committers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Change error message to be able to differentiate the two cases.
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Put a CHECK_FOR_INTERRUPTS call into the loops that try to find a