Re: [patch] ALTER RENAME and indexes - Mailing list pgsql-hackers

From Brent Verner
Subject Re: [patch] ALTER RENAME and indexes
Date
Msg-id 20011007191629.A1983@rcfile.org
Whole thread Raw
In response to Re: [patch] ALTER RENAME and indexes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 07 Oct 2001 at 10:56 (-0400), Tom Lane wrote:
| It occurs to me that the real problem is not so much ALTER RENAME not
| doing enough, as it is psql doing the wrong thing.  The \d display for
| indexes is almost entirely unhelpful, since it doesn't tell you such
| critical stuff as whether the index is a functional index nor which
| index opclasses are being used.  I wonder whether we oughtn't rip out
| the whole display and make it report the results of pg_get_indexdef(),
| instead.

This would solve the display problem for sure, but we'd still have
bad data in the pg_attribute tuple for the index -- specifically, 
attname would still contain the original column name that the index
was created on.  I'm now aware that PG does not use this attname
directly/internally, but it would still be wrong if anyone happens
to look at the system catalog.

cheers. Brent

-- 
"Develop your talent, man, and leave the world something. Records are 
really gifts from people. To think that an artist would love you enough
to share his music with anyone is a beautiful thing."  -- Duane Allman


pgsql-hackers by date:

Previous
From: Kovacs Baldvin
Date:
Subject: Secure enough to use CVS version?
Next
From: "Kelly Harmon"
Date:
Subject: Accessing Database files on a "read-only" medium...like a CD.