I'm working with two different postgres installations - they're both
v7.1.2. On one I can drop a table and the related constraint info seems to
go away with the table, on the other the restraint trigger seems to remain
in the system tables and then when I try to delete rows from tables once
At 01:30 PM 7/6/2001 -0700, you wrote:
On Fri, 6 Jul 2001, Somazx Interesting wrote:
I'm working with two different postgres installations - they're both
v7.1.2. On one I can drop a table and the related constraint info seems to
go away with the table, on the other the restraint trigger
It would seem that my postgresql database system is getting slower and
slower at dropping tables and possibly other tasks too.
Am I being paranoid? I don't think so.
Can anyone think of anything that would cause dropping a table with little
data contained within it to take several seconds
At 02:18 PM 6/8/2001 -0400, Tom Lane wrote:
Somazx Interesting [EMAIL PROTECTED] writes:
getTables(): SELECT (funcname) for trigger sa_eval_trigger_608 returned 0
tuples. Expected 1.
pg_dump failed on OnEd, exiting
Kinda looks like you dropped some function that was still referenced
At 01:30 PM 6/8/2001 -0700, you wrote:
At 02:18 PM 6/8/2001 -0400, Tom Lane wrote:
Somazx Interesting [EMAIL PROTECTED] writes:
getTables(): SELECT (funcname) for trigger sa_eval_trigger_608
returned 0
tuples. Expected 1.
pg_dump failed on OnEd, exiting
This is easy to fix
Can anyone help me with this error message I get when I attempt to dump my
database?
[dfunct@localhost dfunct]$ pg_dumpall
/home/dfunct/OnEd_backups/OnEd_Wednesday.sql
getTables(): SELECT (funcname) for trigger sa_eval_trigger_608 returned 0
tuples. Expected 1.
pg_dump failed on OnEd,
It would seem that my postgresql database system is getting slower and
slower at dropping tables and possibly other tasks too.
Am I being paranoid? I don't think so.
Can anyone think of anything that would cause dropping a table with little
data contained within it to take several seconds
