| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: master in standby mode croaks |
| Date: | 2010-04-17 22:52:35 |
| Message-ID: | s2p603c8f071004171552z8cd74a28y606813c1b22f822c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Apr 17, 2010 at 6:41 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Sat, 2010-04-17 at 17:44 -0400, Robert Haas wrote:
>
>> > I will change the error message.
>>
>> I gave a good deal of thought to trying to figure out a cleaner
>> solution to this problem than just changing the error message and
>> failed. So let's change the error message. Of course I'm not quite
>> sure what we should change it TO, given that the situation is the
>> result of an interaction between three different GUCs and we have no
>> way to distinguish which one(s) are the problem.
>
> "You need all three" covers it.
Actually you need standby_connections and either archive_mode=on or
max_wal_senders>0, I think.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-04-18 03:23:28 | enable_material patch |
| Previous Message | Tom Lane | 2010-04-17 22:52:26 | Re: testing HS/SR - 1 vs 2 performance |