Victor S. (vicsanca(at)idieikon(dot)com) reports a bug with a severity of 1
The lower the number the more severe it is.
pg_dump don't works with many tables
Sorry about the last two messages. We have finally identified when the error happens. We have near 1000 tables with 3 foreings keys to three tables. Example:
Table 1--- foreign keys to A, B and C
Table 2--- foreign keys to A, B and C
Table 3--- foreign keys to A, B and C
Table 1000--- foreign keys to A, B and C
PostgreSQL works fine but if we try to do a pg_dump of the database (in verbose for debug the error) mode it breaks after 10 minutes(aprox.) when pg_dump is finding triggers for table A. The process exits with a "Killed" message.
With the same 1000 tables witout foreign keys it works fine.
Whe have tested it with PostgreSQL 7.1, 7.2 and 7.2.1 under linux systems.
Please contact us for more info if wou want.
IDI EIKON S.L.
Another questions: Commercial support cover this type of errors?
No file was uploaded with this report
pgsql-bugs by date
|Next:||From: pgsql-bugs||Date: 2002-06-07 16:20:11|
|Subject: Bug #686: growing tables|
|Previous:||From: Bruce Momjian||Date: 2002-06-07 05:39:18|
|Subject: Re: Bug #668: cursors with params: mismatched parentheses;|