| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Nikita The Spider The Spider" <nikitathespider(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 5 minutes to pg_dump nothing |
| Date: | 2007-09-21 16:36:53 |
| Message-ID: | 6682.1190392613@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Nikita The Spider The Spider" <nikitathespider(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Jones | 2007-09-21 16:52:11 | Migrating from 32 bit to 64 bit binaries |
| Previous Message | Tom Lane | 2007-09-21 16:14:37 | Re: foreign key on views |