| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Ivan Zolotukhin <ivan(dot)zolotukhin(at)gmail(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL General <pgsql-general(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: pg_start_backup() takes too long |
| Date: | 2008-10-01 06:27:05 |
| Message-ID: | 1222842425.4445.1403.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2008-09-30 at 12:58 +0400, Ivan Zolotukhin wrote:
> Just a few points on pg_start_backup() from user point of view. I
> personally would prefer to have some control over the process, e.g. it
> would be nice to have proposed pg_start_backup(label text,
> immediate_chkpt boolean).
I've added this function to Infrastructure Changes for Recovery (v8)
patch, with a NOTICE message as suggested also. Seemed easier to work on
it while I was there.
No changes to bgwriter smoothing.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darragh Gammell | 2008-10-01 06:33:21 | tsearch2 Upgrade to 8.3 tsearch2.so errors |
| Previous Message | Roshni Mani | 2008-10-01 06:13:53 | error compiling postgres source |