|
Home > Archive > Pgadmin > October 2006 > Deleting an index confuses SQL dialogue window
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Deleting an index confuses SQL dialogue window
|
|
| Erwin Brandstetter 2006-10-28, 12:47 am |
| Hi Dave,
the last thing I want is to mess with your blood pressure, but I
just might have another one here ...
If I run a query in the SQL dialogue window which utilizes an index and
delete this index afterwards, the same query will result in an error
after that.
FEHLER: could not open relation with OID 1134569
SQL state: XX000
Context: SQL-Anweisung »SELECT (...)
Recreating the index under the same name does not help, as pgAdmin seems
to be looking for the OID of the index. It seems the query plan is being
saved and executed over and over again. Executing other queries in the
same SQL dialogue window works fine. Trying the original query keeps
failing.
Executing the same query in a new SQL dialogue window works fine.
Not sure if this is a bug or by design. It certainly looks like a bug to me.
Regards
Erwin
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
| |
| Dave Page 2006-10-28, 7:33 pm |
|
> If I run a query in the SQL dialogue window which utilizes an index and delete
> this index afterwards, the same query will result in an error after that.>
>
> FEHLER: could not open relation with OID 1134569
> SQL state: XX000
> Context: SQL-Anweisung »SELECT (...)
>
> Recreating the index under the same name does not help, as pgAdmin seems to be
> looking for the OID of the index. It seems the query plan is being saved and
> executed over and over again. Executing other queries in the same SQL dialogue
> window works fine. Trying the original query keeps failing.
>
> Executing the same query in a new SQL dialogue window works fine.
>
> Not sure if this is a bug or by design. It certainly looks like a bug to me.
That error is coming from PostgreSQL - the query tool never looks at any
indexes; it just sends the query and displays whatever comes back. What is
the exact sequence of events needed to reproduce this?
Regards, Dave.
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
|
|
|
|
|