Re: Plans for index names unique to a table?
Jim Nasby <jim@nasby.net>
From: "Jim C. Nasby" <jim@nasby.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Sean Chittenden <sean@chittenden.org>, pgsql-hackers@postgresql.org
Date: 2003-05-10T15:53:09Z
Lists: pgsql-hackers
On Fri, May 09, 2003 at 12:07:13AM -0400, Tom Lane wrote: > Sean Chittenden <sean@chittenden.org> writes: > > Are there any plans to make index names unique to a table instead of > > to a schema? > > None on my plate ... I don't see any very reasonable way to do it. > Do you? What makes it unreasonable? How are constraints handled differently that makes it reasonable for them? I can think of two ways to handle this... a) Leave indexes in pg_class and add a field to indicate the table/object that the item belongs to. relnamespace could very possebly be used for this. b) Create a seperate table for indexes. Of course, it's trivial to change a few system tables, it's changing everything else in code that will be the fun part. :) I'm hoping that plan a wouldn't impact the internals too badly, but I really have no idea. FWIW, DB2 and (I think) Oracle both use a global namespace for indexes. Sybase and (I think) MSSQL don't. I really don't understand why you'd want indexes in a global namespace and wish IBM and Oracle would change their products. -- Jim C. Nasby (aka Decibel!) jim@nasby.net Member: Triangle Fraternity, Sports Car Club of America Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"