Re: A deprecation policy - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: A deprecation policy
Date
Msg-id 499288AA.9030403@enterprisedb.com
Whole thread Raw
In response to A deprecation policy  (Peter Eisentraut <peter_e@gmx.net>)
List 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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pg_upgrade project status
Next
From: Markus Wanner
Date:
Subject: Re: A deprecation policy