From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org, Simon Riggs <simon(at)2ndquadrant(dot)com> |
Subject: | Re: [PATCHES] Doc update for pg_start_backup |
Date: | 2007-06-29 03:35:53 |
Message-ID: | 3833.1183088153@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> Added a note to the docs that pg_start_backup can take a long time to
> finish now that we spread out checkpoints:
I was starting to wordsmith this, and then wondered whether it's not
just a stupid idea for pg_start_backup to act that way. The reason
you're doing it is to take a base backup, right? What are you going
to take the base backup with? I do not offhand know of any backup
tools that don't suck major amounts of I/O bandwidth. That being
the case, you're simply not going to schedule the operation during
full-load periods. And that leads to the conclusion that
pg_start_backup should just use CHECKPOINT_IMMEDIATE and not slow
you down.
Thoughts?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-06-29 07:04:45 | Re: [PATCHES] Doc update for pg_start_backup |
Previous Message | Tom Lane | 2007-06-29 03:18:05 | Re: AutoVacuum Behaviour Question |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-06-29 07:04:45 | Re: [PATCHES] Doc update for pg_start_backup |
Previous Message | Andrew Dunstan | 2007-06-29 01:55:17 | Re: WIP CSV logs |