Re: change of table name - any help

Christoph,
Thx for your response. We didn't change the search_parth variable. Moreover,
I tried all combination of drop statements like

Drop table table_name
Drop table owner.table_name
Drop table "table_name"
Drop table "owner.table_name"

I don't know what is the problem. Somebody in this esteemed group suggested
me to write to Mr. Tom lane (since he understand the catalog very well) and
I did that and waiting for his response on this issue.
Rgds
--Ranga

-----Original Message-----
From: ch(at)rodos(dot)fzk(dot)de [mailto:ch(at)rodos(dot)fzk(dot)de]
Sent: Friday, September 19, 2003 2:37 AM
To: pgsql-hackers(at)postgresql(dot)org; ranga(at)dvdstation(dot)com

> We have a development server running
>
> OS - Linux development-server 2.4.20-openmosix-r4 #1 SMP Mon May 19
02:32:52
> PDT 2003 i686 Intel(R) Xeon(TM) CPU 2.40GHz GenuineIntel GNU/Linux
>
> Database - PostgreSQL 7.3 on i686-pc-linux-gnu, compiled by GCC gcc
(GCC)
> 3.2.1
>
> We have a table ctcert_name under postgres DB(postgres schema and
postgres
> user is the owner). Suddenly, this object started missing from the DB
(I am
> the only
>
> Person who connects to that server and did not drop/renamed it). When
I
> tried to recreate the same table, the system threw me back an error,
saying
> that "postgres.ctcert_name" already exists. I am neither able to drop
or
> rename the table.
>
> checked the DB logs and there is no drop/rename table statement in
that.
>
> I have the transaction logs, but not able to read, as they are not in
the
> human readable format.
>
> How can I decipher from the txn logs, if it captures the change
management.
>
> Can somebody please tell me, what cud have gone wrong and is the error
is
> reproduceable? What is the solution for this kind of problem.
>
Did you change the SEARCH_PATH variable?
Did I get this right:
You cannot
DROP TABLE postgres.ctcert_name ;
Mind, I left off the enclosing quotes.
And you cannot
CREATE TABLE postgres.ctcert_name( ... ) ;

My suspicion is you are using these quotes and you shouldn't.

Regards, Christoph