| From: | Joshua Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: unite recovery.conf and postgresql.conf |
| Date: | 2011-09-25 20:13:20 |
| Message-ID: | 1306461547.50992.1316981600939.JavaMail.root@mail-1.01.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I rather like Tom's suggestion of include_if_exists.
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.
--Josh Berkus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-09-25 20:17:30 | Re: unite recovery.conf and postgresql.conf |
| Previous Message | Dimitri Fontaine | 2011-09-25 20:09:25 | Re: [v9.2] DROP statement reworks |