On Sat, 2003-04-26 at 15:02, Tom Lane wrote:
Hi Tom,
PostgreSQL 7.3.2's pg_dump utility was able to completely dump out the
schema with out core dumping, and the queries that were being output to
the log file were very different from those used by PostgreSQL 7.2.4's
pg_dump utility. v7.2 seemed to get past the schema checks and was doing
queries on the data in the tables, but then it just quite litterally
puttered out... :>
> Chris Bowlby <excalibur@hub.org> writes:
> > Ok, running the select statement that was used in the core file, I get
> > [ normal results ]
>
> Okay, scratch that theory. Looking at it a second time, I now think
> this particular select is not directly at fault, but is simply losing
> because pg_dump is out of memory (a condition libpq has never tolerated
> very well :-(). But that still leaves us with the question of where the
> memory went. The stack trace shows that pg_dump is still collecting
> schema information, and hasn't begun pulling down the contents of user
> tables --- but how could it chew up 512Mb on schema information?
>
> I would suggest turning on query logging (look in postgresql.conf) and
> re-running pg_dump. Perhaps a look at the series of queries it issues
> will show that it's gotten stuck in a loop somewhere.
>
> Another test that would be useful, if you happen to have a 7.3
> installation handy, is to see if 7.3 pg_dump can dump this database.
>
> regards, tom lane
--
Chris Bowlby <excalibur@hub.org>
Hub.Org Networking Services