From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER TABLE TODO items |
Date: | 2004-05-06 13:50:52 |
Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB34101AE08@Herge.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Two very minor points with the new alter table (not sure if they are
even bugs are have already been addressed).
1. alter table alter type on a clustered index seems to drop the cluster
(by design)?
2. alter table cluster on seems to give a strange error message of the
index name is really the name of a table.
Ex:
alter table test cluster on test;
returns:
ERROR: cache lookup failed for index 19013
Merlin
Log:
test=# create table test (id int);
CREATE TABLE
test=# create index test_id_idx on test(id);
CREATE INDEX
test=# alter table test cluster on test;
ERROR: cache lookup failed for index 19046
test=# alter table test cluster on test_id_idx;
ALTER TABLE
test=# \d test
Table "public.test"
Column | Type | Modifiers
--------+---------+-----------
id | integer |
Indexes:
"test_id_idx" btree (id) CLUSTER
test=# alter table test alter id type bigint;
ALTER TABLE
test=# \d test
Table "public.test"
Column | Type | Modifiers
--------+--------+-----------
id | bigint |
Indexes:
"test_id_idx" btree (id)
test=#
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2004-05-06 14:17:31 | Re: Bug in pg_dump 7.4 |
Previous Message | Darko Prenosil | 2004-05-06 13:38:10 | Bug in pg_dump 7.4 |