| From: | "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at> |
|---|---|
| To: | "Richard Huxton *EXTERN*" <dev(at)archonet(dot)com>, "Bruce McAlister" <bruce(dot)mcalister(at)blueface(dot)ie> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Recovery/Restore and Roll Forward Question. |
| Date: | 2007-06-21 10:41:07 |
| Message-ID: | AFCCBB403D7E7A4581E48F20AF3E5DB20379EAC4@EXADV1.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Richard Huxton wrote:
>> In our environment it takes approx 2 hours to perform a PIT backup of
>> our live system:
>>
>> [1] select pg_start_backup('labe;')
>> [2] cpio & compress database directory (exclude wals)
>> [3] select pg_stop_backup()
>>
>> However, if we perform a plain dump (pg_dump/pg_dumpall) we
>> can dump the whole lot in 15 minutes. For us this is more efficient.
>
> It sounds like there's something strange with your setup if it's
quicker
> for pg_dump to read your data than cp. Do you have *lots* of indexes,
or
> perhaps a lot of dead rows?
That sounds like a good bet.
Did you ever do a VACUUM FULL?
What is the size of the online backup?
What is the size of the pg_dumpall?
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Henka | 2007-06-21 10:44:30 | 8.2.3 PANIC with "corrupted item pointer" |
| Previous Message | Richard Huxton | 2007-06-21 10:30:29 | Re: Recovery/Restore and Roll Forward Question. |