| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com> |
| Subject: | Re: Summary of plans to avoid the annoyance of Freezing |
| Date: | 2015-09-09 13:03:19 |
| Message-ID: | CAM-w4HO7CK2PgzQWdn8DeYdCWYdV5v7sK_K=WtBMf-XxGyhfig@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Sep 6, 2015 at 1:25 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> My vote is that we should try to get freeze maps into 9.6 - that seems
> more realistic given that we have a patch right now. Yes, it might end
> up being superflous churn, but it's rather localized. I think around
> we've put off significant incremental improvements off with the promise
> of more radical stuff too often.
Superfluous churn in the code isn't too bad. But superfluous churn in
data formats might be a bit more scary. Would we be able to handle
pg_upgrade from a database with or without a freezemap? Would you have
to upgrade once to add the freezemap then again to remove it?
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2015-09-09 13:13:04 | Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file |
| Previous Message | Stephen Frost | 2015-09-09 12:41:53 | Re: pgsql: Improve logging of TAP tests. |