| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: hot_standby = on |
| Date: | 2010-06-08 20:54:58 |
| Message-ID: | 4C0EAE22.5010903@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> On Thu, Jun 3, 2010 at 11:15 PM, Andrew Dunstan
> <andrew(dot)dunstan(at)pgexperts(dot)com> wrote:
>
>> The docs don't seem to contain any discussion I could find on why one might
>> not want hot_standby on. Maybe it's just too obvious to most people, but
>> this seems to be a bit lacking in the docs.
>>
>
> Well, if you don't want your slave to process queries, then you
> wouldn't turn it on, presumably.
>
>
Well, yes. But then to stop that you could just lock users out using
pg_hba.conf, no? It just doesn't seem to be buying all that much to me.
It's not a big deal, I was just curious. There are all these new knobs
to play with ...
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-06-08 20:55:01 | Re: Idea for getting rid of VACUUM FREEZE on cold pages |
| Previous Message | Robert Haas | 2010-06-08 20:47:06 | Re: primary/secondary/master/slave/standby |