| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | chris <cbbrowne(at)ca(dot)afilias(dot)info> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: pg_dump additional options for performance |
| Date: | 2008-08-02 15:24:01 |
| Message-ID: | 3677.1217690641@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
chris <cbbrowne(at)ca(dot)afilias(dot)info> writes:
> Do we need to wait until a fully-parallelizing pg_restore is
> implemented before adding this functionality to pg_dump?
They're independent problems ... and I would venture that parallel
dump is harder.
> Further, it's actually not obvious that we *necessarily* care about
> parallelizing loading data. The thing that happens every day is
> backups.
Maybe so, but I would say that routine backups shouldn't be designed
to eat 100% of your disk bandwidth anyway --- they'd be more like
background tasks.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-08-02 15:38:48 | Re: Parsing of pg_hba.conf and authentication inconsistencies |
| Previous Message | Andrew Dunstan | 2008-08-02 14:27:21 | Re: [HACKERS]odd output in restore mode |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2008-08-02 18:38:46 | Re: WITH RECUSIVE patches 0723 |
| Previous Message | Andrew Dunstan | 2008-08-02 14:27:21 | Re: [HACKERS]odd output in restore mode |