| From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Samrat Revagade <revagade(dot)samrat(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch for fail-back without fresh backup |
| Date: | 2013-10-24 12:40:58 |
| Message-ID: | CABOikdP94TY0ku257BFAPi-XprY9cQCHnBfRvEWcOh-z7yshdw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 24, 2013 at 5:45 PM, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com
> wrote:
>
>>
> Will just have to figure out what we want the user interface to be like;
> should it be a separate guc, or somehow cram it into wal_level?
>
>
Yeah, I had brought up similar idea up thread. Right now wal_level is
nicely ordered. But with this additional logic, I am not sure if we would
need multiple new levels and also break that ordering (I don't know if its
important). For example, one may want to set up streaming replication
with/without this feature or hot standby with/without the feature. I don't
have a good idea about how to capture them in wal_level. May be something
like: minimal, archive, archive_with_this_new_feature, hot_standby and
hot_standby_with_this_new_feature.
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2013-10-24 13:06:19 | Re: [PATCH] Use MAP_HUGETLB where supported (v3) |
| Previous Message | Heikki Linnakangas | 2013-10-24 12:15:51 | Re: Patch for fail-back without fresh backup |