On tis, 2011-03-15 at 20:44 +0200, Peter Eisentraut wrote:
Consequently, I propose the attached patch. I didn't find any
relevant documentation references that would need updating.
Applied.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
I looked through this, and it appears that we can just remove these
restrictions.
I considered the following parameters, which are measured in
milliseconds and currently have INT_MAX/1000 as maximum value.
deadlock_timeout
max_standby_archive_delay
max_standby_streaming_delay
FYI, this is now on the TODO list:
Increase maximum values for max_standby_streaming_delay and
log_min_duration_statement
* http://archives.postgresql.org/pgsql-hackers/2010-12/msg01517.php
On Fri, Mar 4, 2011 at 18:19, Robert Treat r...@xzilla.net wrote:
On Fri, Mar 4, 2011 at 2:03 AM, Magnus Hagander mag...@hagander.net wrote:
On Fri, Mar 4, 2011 at 04:00, Robert Treat r...@xzilla.net wrote:
I have a server where I wanted to do some reporting on a standby, and
wanted to set the
On Fri, Mar 4, 2011 at 2:03 AM, Magnus Hagander mag...@hagander.net wrote:
On Fri, Mar 4, 2011 at 04:00, Robert Treat r...@xzilla.net wrote:
I have a server where I wanted to do some reporting on a standby, and
wanted to set the max standby delay to 1 hour. upon doing that, i get
this in the
I have a server where I wanted to do some reporting on a standby, and
wanted to set the max standby delay to 1 hour. upon doing that, i get
this in the logs:
2011-03-03 21:20:08 EST () [2656]: [2-1] user=,db=LOG: received
SIGHUP, reloading configuration files
2011-03-03 21:20:08 EST () [2656]:
On Fri, Mar 4, 2011 at 04:00, Robert Treat r...@xzilla.net wrote:
I have a server where I wanted to do some reporting on a standby, and
wanted to set the max standby delay to 1 hour. upon doing that, i get
this in the logs:
2011-03-03 21:20:08 EST () [2656]: [2-1] user=,db=LOG: received
