Hi,
After stopping the eecution of some external program which use postgre, one
temporary table wasnt automatically erased.
It still exists in pg_temp_14 schema.
May i drop that table and that schema manually? (will it cause some
problems)?
Thanx in advance
--
---
Kevin Kempter writes:
> anyone know what would cause errors like this (postgres version 8.1.15):
> drop table bigtab1;
>
> ERROR: could not find tuple for constraint 373617
> drop sequence bigtab2_id_seq;
Hi all;
anyone know what would cause errors like this (postgres version 8.1.15):
drop table bigtab1;
ERROR: could not find tuple for constraint 373617
drop sequence bigtab2_id_seq;
"Daniel Cristian Cruz" <[EMAIL PROTECTED]> writes:
> I had a problem today, where pg_dump was locking a concurrent DROP TABLE,
> and it was another table, not the table in the COPY running. Is it normal?
Yes. pg_dump acquires ACCESS SHARE lock on all the tables it's
intending to dump. Without th
Helllo,
I had a huge database with a dump backup routine.
I had a problem today, where pg_dump was locking a concurrent DROP TABLE,
and it was another table, not the table in the COPY running. Is it normal?
Some kind of bug or is it expected?
I'm using 8.2.4 (I need to rewrite dblink functions b
I am running 7.4.2,
when I try to drop a table it comes back with the message:
relation
"vm-message" has reltriggers = 0
and doesn't drop the
table. What does this mean and how can I really drop the
table?
Chris
White
On Mon, Jun 03, 2002 at 12:59:27PM -0300, Juan Rojas wrote:
> Hi,
> I'm running PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96.
> I have a problem when I drop a table which contains a serial field. The
> system drops the table but the associated sequence still remains in the
> catalog
Title: drop table failed to drop associated sequence
Hi,
I'm running PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96.
I have a problem when I drop a table which contains a serial field. The system drops the table but the associated sequence still remains in the catalog, so if I wan
well, in all my wisdom and quick typing, i dropped a main table rather than
the one i meant to drop. this just happened. can i recover it with some
quick statement i have an actual backup on tape from last night --
not a pgdump but a physical backup of the files in the database direc
