Skip site navigation (1) Skip section navigation (2)

Re: Bug #685: pg_dump don't works with many tables

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: vicsanca(at)idieikon(dot)com, pgsql-bugs(at)postgresql(dot)org,pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #685: pg_dump don't works with many tables
Date: 2002-06-10 01:44:58
Message-ID: 5.1.0.14.0.20020610114342.04f21cb0@mail.rhyme.com.au (view raw or flat)
Thread:
Lists: pgsql-bugs
At 06:30 7/06/02 -0400, pgsql-bugs(at)postgresql(dot)org wrote:
>Victor S. (vicsanca(at)idieikon(dot)com) reports a bug with a severity of 1
>
>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.


What was the last thing it did? Can you send a backtrace?


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 0500 83 82 82         |                 ___________ |
Http://www.rhyme.com.au          |                /           \|
                                  |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/


In response to

pgsql-bugs by date

Next:From: pgsql-bugsDate: 2002-06-10 02:40:37
Subject: Bug #687: cannot " create table copy (..."
Previous:From: Ingo van LilDate: 2002-06-08 15:26:15
Subject: Re: Postgres Reference Manual

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group