| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bug in 7.4 SET WITHOUT OIDs |
| Date: | 2004-06-09 02:02:37 |
| Message-ID: | 40C66FBD.6050501@familyhealth.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Yep, Tom fixed it good.
Bruce Momjian wrote:
> I can confirm that current CVS handles this OK.
>
> ---------------------------------------------------------------------------
>
> Christopher Kings-Lynne wrote:
>
>>I had a suspicion and it was confirmed:
>>
>>test=# create table oidtest (a int4, unique(oid));
>>NOTICE: CREATE TABLE / UNIQUE will create implicit index
>>"oidtest_oid_key" for table "oidtest"
>>CREATE TABLE
>>test=# select oid from oidtest;
>> oid
>>-----
>>(0 rows)
>>
>>test=# alter table oidtest set without oids;
>>ALTER TABLE
>>test=# select oid from oidtest;
>>ERROR: column "oid" does not exist
>>test=# \d oidtest
>>ERROR: cache lookup failed for attribute -2 of relation 765798
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-06-09 03:36:37 | Assignment to array elements |
| Previous Message | Bruce Momjian | 2004-06-09 01:32:51 | Re: bug in 7.4 SET WITHOUT OIDs |