pgsql: Put a CHECK_FOR_INTERRUPTS call into the loops that try to find a

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Put a CHECK_FOR_INTERRUPTS call into the loops that try to find a
Date: 2008-02-20 17:44:14
Message-ID: 20080220174414.8E807754108@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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.

Tags:
----
REL8_3_STABLE

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

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-02-20 17:44:20 pgsql: Put a CHECK_FOR_INTERRUPTS call into the loops that try to find a
Previous Message Tom Lane 2008-02-20 17:44:09 pgsql: Put a CHECK_FOR_INTERRUPTS call into the loops that try to find a