Skip site navigation (1) Skip section navigation (2)

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:09
Message-ID: 20080220174409.767DD754108@cvs.postgresql.org (view raw or flat)
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.

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

Next:From: Tom LaneDate: 2008-02-20 17:44:14
Subject: pgsql: Put a CHECK_FOR_INTERRUPTS call into the loops that try to find a
Previous:From: Alvaro HerreraDate: 2008-02-20 16:48:40
Subject: Re: pgsql: Change error message to be able todifferentiate the two cases.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group