From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: hot_standby = on |
Date: | 2010-06-08 22:33:01 |
Message-ID: | 4C0EC51D.8090509@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> 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.
>>
>
> The main reason to turn it off is to disable a whole lot of very poorly
> tested code, and thereby improve the reliability of your warm standby
> server. There might be (almost certainly are) significant performance
> benefits as well. I think it'll be at least a couple of release cycles
> before any sane DBA would turn it on on standbys where he didn't
> positively need it.
>
>
>
OK, then we need to say something like that. Right now we're not giving
any guidance that I can see.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-06-08 22:35:00 | Re: Idea for getting rid of VACUUM FREEZE on cold pages |
Previous Message | Andrew Dunstan | 2010-06-08 22:30:38 | Re: Command to prune archive at restartpoints |