[GENERAL] Cluster means tangle for me
I would appreciate any advice on getting out of this strange situation. My table now doesn't exist, but I can't recreate it either (at least under that name). jeffe@kiyoko= psql -V psql (PostgreSQL) 7.0.0 jeffe@kiyoko= uname -a FreeBSD kiyoko.la.verio.net 4.0-STABLE FreeBSD 4.0-STABLE #0: Thu Apr 27 10:44:07 CDT 2000 extracts=# create index dc_et_i on dedcolo (equip_type); CREATE extracts=# cluster dc_et_i on dedcolo; ERROR: temp_286bbc3 is an index relation extracts=# drop index dc_et_i; ERROR: index "dc_et_i" nonexistent extracts=# \d dedcolo Did not find any relation named "dedcolo". extracts=# vacuum verbose analyze; (snip) NOTICE: mdopen: couldn't open temp_28421e0: No such file or directory NOTICE: RelationIdBuildRelation: smgropen(temp_28421e0): No such file or directory NOTICE: --Relation temp_28421e0-- NOTICE: mdopen: couldn't open temp_28421e0: No such file or directory ERROR: cannot open relation temp_28421e0 extracts=# drop table temp_28421e0; NOTICE: mdopen: couldn't open temp_28421e0: No such file or directory NOTICE: mdopen: couldn't open temp_28421e0: No such file or directory NOTICE: mdopen: couldn't open temp_28421e0: No such file or directory
Re: [GENERAL] Cluster means tangle for me
Jeff Eckermann [EMAIL PROTECTED] writes: I would appreciate any advice on getting out of this strange situation. My table now doesn't exist, but I can't recreate it either (at least under that name). Hmm, was "dedcolo" a temp table? It looks like clustering a temp table gets confused. (In current sources, it's still pretty broken: the cluster succeeds, but the table is no longer temp afterwards ... will try to fix this for 7.1.) I'd suggest that you restart your session, then repeat the vacuum, and for each table that you get "mdopen" notices about, create an empty file by that name in the database directory. Then you'll be able to drop that table. regards, tom lane
