From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Allowing multiple concurrent base backups |
Date: | 2011-01-25 04:02:19 |
Message-ID: | AANLkTikp1baK60=p4Tgh5C3KvR_PNF3ZsPNQmwBgLSHK@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 25, 2011 at 6:02 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> Hmm, perhaps the code would be more readable if instead of the
> forcePageWrites counter that counts exclusive and non-exclusive backups, and
> an exclusiveBackup boolean indicating if one of the in-progress backups is
> an exclusive one, we had a counter that only counts non-exclusive backups,
> plus a boolean indicating if an exclusive backup is in progress in addition
> to them.
>
> Attached is a patch for that (against master branch, including only xlog.c).
I read this patch and previous-posted one. Those look good.
Comments:
+ * do_pg_start_backup is the workhorse of the user-visible pg_stop_backup()
+ * function.
Typo: s/do_pg_start_backup/do_pg_stop_backup
It's helpful to explain about this behavior in pg_basebackup.sgml or elsewhere.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2011-01-25 04:13:29 | Re: ALTER TYPE 3: add facility to identify further no-work cases |
Previous Message | Fujii Masao | 2011-01-25 03:45:33 | Re: Allowing multiple concurrent base backups |