Re: 5 minutes to pg_dump nothing - Mailing list pgsql-general

From Tom Lane
Subject Re: 5 minutes to pg_dump nothing
Date
Msg-id 6682.1190392613@sss.pgh.pa.us
Whole thread Raw
In response to 5 minutes to pg_dump nothing  ("Nikita The Spider The Spider" <nikitathespider@gmail.com>)
Responses Re: 5 minutes to pg_dump nothing  ("Nikita The Spider The Spider" <nikitathespider@gmail.com>)
List pgsql-general
"Nikita The Spider The Spider" <nikitathespider@gmail.com> writes:
> I'm seeing a problem where pg_dump takes at least 5 minutes to execute
> no matter what I ask it to dump -- even a non-existent or empty table.
> One possible red flag is that pg_type contains 56508 rows. This
> doesn't seem excessive to me, but perhaps it should.

That does seem like a lot --- what sort of types are they?  Scalar,
composite, what?  It's fairly likely that no one has tried to optimize
pg_dump for such a case.

It'd be helpful if you could recompile pg_dump with profiling enabled
(-pg compiler switch) and get a gprof profile to show where the time
is going.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: foreign key on views
Next
From: Erik Jones
Date:
Subject: Migrating from 32 bit to 64 bit binaries