Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f2UFr5K69907 for ; Fri, 30 Mar 2001 10:53:05 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id KAA22347; Fri, 30 Mar 2001 10:52:52 -0500 (EST) From: Bruce Momjian Message-Id: <200103301552.KAA22347@candle.pha.pa.us> Subject: Re: [SQL] Re: pg_dump potential bug -UNIQUE INDEX on PG_SHADOW Dont!! HELP In-Reply-To: <99us31$cvk$1@news.tht.net> "from Marcin Kowalski at Mar 29, 2001 10:35:06 am" To: Marcin Kowalski Date: Fri, 30 Mar 2001 10:52:52 -0500 (EST) CC: PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200103/1531 X-Sequence-Number: 6903 I can confirm with current sources: test=> CREATE UNIQUE INDEX shadow_index ON pg_shadow (usename); CREATE test=> select * from pg_shadow; ERROR: Index 'pg_shadow_sysid_index' does not exist test=> \q $ psql test psql: FATAL 1: Index 'pg_shadow_name_index' does not exist $ gdb shows that the check in heap_create() is working because the index name does not begin with pg_, just the base table: Breakpoint 1, heap_create (relname=0x838d1d0 "shadow_index", tupDesc=0x83915e4, istemp=0 '\000', storage_create=0 '\000', allow_system_table_mods=0) at heap.c:183 183 bool nailme = false; First, should we allow user-specified indexes on system tables, and if so, why does this error happen? Notice the user wanted an index named shadow_index, but the error mentioned is pg_shadow_name_index. > Hi > > Regarding my previous post, I just successfully created a unique index on > pg_shadow. DON'T DO THIS!!! > ------- > CREATE UNIQUE INDEX shadow_index ON pg_shadow (usename) > ------- > I couldn't create at pg_shadow_index as the pg prefix is reserved for > system tables. > > This BROKE the database. At least I can't connect anymore with a: > ------- > template1=# \c statements > FATAL 1: Index 'pg_shadow_name_index' does not exist > Previous connection kept > template1=# > ------- > If I look at the error log I get : > ------- > ERROR: Illegal class name 'pg_shadow_index' > The 'pg_' name prefix is reserved for system catalogs > ERROR: Index 'pg_shadow_name_index' does not exist > ERROR: SearchSysCache: recursive use of cache 23 > ERROR: SearchSysCache: recursive use of cache 23 > ERROR: SearchSysCache: recursive use of cache 23 > ERROR: SearchSysCache: recursive use of cache 23 <-- quite psql here > FATAL 1: Index 'pg_shadow_name_index' does not exist <-- restarted again > FATAL 1: Index 'pg_shadow_name_index' does not exist > FATAL 1: Index 'pg_shadow_name_index' does not exist > ------- > > What can I do??? I've got a non-trivial amount of data that I cannot afford > to lose!! HELP!.. > > Regards > MArCin - Thanks > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026