Joshua Berkus <j...@agliodbs.com> writes:
> include_if_exists certainly solves the recovery.conf/recovery.done problem.
> We can even phase it out, like this:
> 9.2: include_if_exists = 'recovery.conf' in the default postgresql.conf file.
> 9.3: include_if_exists = 'recovery.conf' commented out by default
> 9.4: renaming recovery.conf to recovery.done by core PG code removed.
> This gives users/vendors 3 years to update their scripts to remove dependence
> on recovery.conf. I'm afraid that I agree with Simon that there's already a
> whole buncha 3rd-party code out there to support the current system.
If there is indeed code out there that depends on the current system,
why do you think that waiting several releases to change it will make
things better? I think it's more likely that we'd just have *more* code
that needs to be changed, and no reduction in the pain level when the
transition does finally happen.
In any case, I thought we'd agreed that the use of that file as a flag
should go away now, so I quite fail to understand your comment about 9.4.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
