| From: | Joshua Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Subject: | Re: unite recovery.conf and postgresql.conf |
| Date: | 2011-09-24 19:49:47 |
| Message-ID: | 1890970288.45435.1316893787828.JavaMail.root@mail-1.01.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Since we haven't yet come up with a reasonable way of machine-editing
> postgresql.conf, this seems like a fairly serious objection to
> getting
> rid of recovery.conf. I wonder if there's a way we can work around
> that...
Well, we *did* actually come up with a reasonable way, but it died under an avalanche of bikeshedding and "we-must-do-everything-the-way-we-always-have-done". I refer, of course, to the "configuration directory" patch, which was a fine solution, and would indeed take care of the recovery.conf issues as well had we implemented it. We can *still* implement it, for 9.2.
> pg_ctl start -c work_mem=8MB -c recovery_target_time='...'
This wouldn't survive a restart, and isn't compatible with init scripts.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marti Raudsepp | 2011-09-24 19:57:41 | Re: [PATCH] Log crashed backend's query (activity string) |
| Previous Message | Dimitri Fontaine | 2011-09-24 19:24:49 | Re: [pgsql-advocacy] Unlogged vs. In-Memory |