I tried to reproduce it, but it seems that my problem vanished since i
switched from pg_pconnect to pg_connect in PHP. Maybe this is of any help.
But in my understanding the reported failure should not be influenced by
selection of pg_connect vs. pg_pconnect.
i will report if this problem
Hi Tom, Hi Damon,
Am Dienstag, 27. September 2005 20:36 schrieb Tom Lane:
Damon Hart [EMAIL PROTECTED] writes:
I came across this thread after intermittently observing very similar
error messages last week from a PostgreSQL (8.0.2) server, e.g.:
SQL error: = 'type local_roll already
: type temp_gc already exists
Hi Tom, Hi Damon,
Am Dienstag, 27. September 2005 20:36 schrieb Tom Lane:
Damon Hart [EMAIL PROTECTED] writes:
I came across this thread after intermittently observing very similar
error messages last week from a PostgreSQL (8.0.2) server, e.g.:
SQL error: = 'type
Janning Vygen [EMAIL PROTECTED] writes:
I recently reported this problem and i would like to help solving it. But how
can i build a self-contained test-case? It just happens sometimes under load.
I didn't say you need to make it 100% reproducible; you just have to
make a case that someone else
Hi all -
I came across this thread after intermittently observing very similar
error messages last week from a PostgreSQL (8.0.2) server, e.g.:
SQL error: = 'type local_roll already exists' in line 1984
(only the portion in quotes is generated by the server, the context is
from the client
Damon Hart [EMAIL PROTECTED] writes:
I came across this thread after intermittently observing very similar
error messages last week from a PostgreSQL (8.0.2) server, e.g.:
SQL error: = 'type local_roll already exists' in line 1984
...
Sorry I haven't been able to diagnose this any more
Janning Vygen vygen ( at ) gmx ( dot ) de writes:
Am Samstag, 10. September 2005 18:05 schrieb Tom Lane:
If there's no pg_depend entry then DROP TYPE should work. Otherwise
you might have to resort to manually DELETEing the pg_type row.
Thanks for your detailed answer. I don't want to
Janning Vygen [EMAIL PROTECTED] writes:
$ DROP TYPE temp_gc;
ERROR: type temp_gc does not exist
The temp schema is evidently not in your search path. You need
something like
drop type pg_temp_NNN.temp_gc;
regards, tom lane
---(end of
Am Donnerstag, 15. September 2005 15:31 schrieb Tom Lane:
Janning Vygen [EMAIL PROTECTED] writes:
$ DROP TYPE temp_gc;
ERROR: type temp_gc does not exist
The temp schema is evidently not in your search path. You need
something like
drop type pg_temp_NNN.temp_gc;
great support!
Am Samstag, 10. September 2005 18:05 schrieb Tom Lane:
Janning Vygen [EMAIL PROTECTED] writes:
i guess the table was dropped but not the corresponding type.
How can things like this happen?
Corrupted pg_depend table maybe? You might try REINDEXing pg_depend
to be on the safe side. Also
Janning Vygen [EMAIL PROTECTED] writes:
Am Samstag, 10. September 2005 18:05 schrieb Tom Lane:
If there's no pg_depend entry then DROP TYPE should work. Otherwise
you might have to resort to manually DELETEing the pg_type row.
Thanks for your detailed answer. I don't want to do anything
Hi,
i run postgresql 8.0.3 and i have a script which calls a postgresql function
to calculate a materialized View. this function creates a temp table. It does
so with EXECUTE statments to avoid the caching of plans with temporary
tables. It runs on three servers and evrything went fine for a
Janning Vygen [EMAIL PROTECTED] writes:
i guess the table was dropped but not the corresponding type.
How can things like this happen?
Corrupted pg_depend table maybe? You might try REINDEXing pg_depend
to be on the safe side. Also please look to see if there are any
relevant entries in it
13 matches
Mail list logo
