| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: A deprecation policy |
| Date: | 2009-02-11 08:13:30 |
| Message-ID: | 499288AA.9030403@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> I would also extend this system to removed configuration settings, e.g.,
> max_fsm_*. We should make these deprecated for one release, so (1)
> configuration files can be upgraded without manual work (relevant to
> in-place upgrade), and (2) users are alerted that their carefully
> crafted configuration might need a review.
I'd prefer to have the upgrade tool convert the old configuration file,
comment out max_fsm_* for example. The upgrade tool could well print out
warnings about config file changes. I think you'll have a better chance
of getting the administrators attention when he's running the upgrade
tool than by printing warnings to the log.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wanner | 2009-02-11 08:21:43 | Re: A deprecation policy |
| Previous Message | Peter Eisentraut | 2009-02-11 07:52:25 | Re: pg_upgrade project status |