BUG #1814: Cancelling a CLUSTER changes the OID counter

From: "Ian Burrell" <ianburrell(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #1814: Cancelling a CLUSTER changes the OID counter
Date: 2005-08-08 21:22:26
Message-ID: 20050808212226.D3E83F0B03@svr2.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 1814
Logged by: Ian Burrell
Email address: ianburrell(at)gmail(dot)com
PostgreSQL version: 7.4.6
Operating system: RHEL 3 x86_64
Description: Cancelling a CLUSTER changes the OID counter
Details:

Cancelling a CLUSTER is causing the OID counter to jump forwards. In the
test below, it goes from 108 million to 4286 million (close to 2^32).

We recently wrapped the OID counter.

vodlive=# insert into foo values (1) ;
INSERT 108817614 1
Time: 0.675 ms
vodlive=# select oid, * from foo ;
oid | bar
-----------+-----
108817614 | 1

vodlive=# CLUSTER idx_daily_by_cs_ti_wk_wk_cs_ti ON
daily_xtns_by_cable_sys_title_wk ;
Cancel request sent
ERROR: canceling query due to user request
vodlive=# abort ;
ROLLBACK

vodlive=# insert into foo values (1) ;
INSERT 4286822632 1
Time: 0.475 ms
vodlive=# select oid, * from foo ;
oid | bar
------------+-----
4286822632 | 1
(1 row)

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2005-08-08 23:40:39 Re: BUG #1809: invalid pointer on pg_ctl reload
Previous Message Magnus Hagander 2005-08-08 18:55:36 Re: BUG #1799: Auto Creation of Strong Password fails