Skip site navigation (1) Skip section navigation (2)

Re: hot_standby = on

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
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 21:24:46
Message-ID: 10910.1276032286@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
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.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: David FetterDate: 2010-06-08 21:29:52
Subject: Re: How about closing some Open Items?
Previous:From: Robert HaasDate: 2010-06-08 21:17:34
Subject: Re: Command to prune archive at restartpoints

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group