| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: recovery_connections cannot start (was Re: master in standby mode croaks) |
| Date: | 2010-04-23 23:22:46 |
| Message-ID: | n2y603c8f071004231622pcc48e34azd591ddfb12ee452@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 23, 2010 at 7:12 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Fri, Apr 23, 2010 at 7:07 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Well, there is another variable that they'll have to adjust as well,
>>> but ISTM that archive_mode still does what it did before, ie, determine
>>> whether we attempt to archive WAL segments.
>
>> But it doesn't do EVERYTHING that it did before. Changing the name
>> would make that a lot more clear. Of course I just work here.
>
> I think from the user's point of view it does what it did before.
> The fact that the actual content of WAL changed was an implementation
> detail that users weren't aware of. Now that we have two interacting
> features that affect WAL contents, it's getting too hard to hide that
> from users --- but I see no need to rename archive_mode.
Well, when people use their same settings that they used for 8.4 and
it doesn't work, you can field those reports...
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-04-23 23:28:55 | Re: recovery_connections cannot start (was Re: master in standby mode croaks) |
| Previous Message | Erik Rijkers | 2010-04-23 23:17:22 | Re: testing HS/SR - 1 vs 2 performance |