Search Postgresql Archives

Re: hot_standby_feedback vs. max_standby_archive_delay/max_standby_streaming_delay?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: hot_standby_feedback vs. max_standby_archive_delay/max_standby_streaming_delay?
From: Steve Kehlet <steve.kehlet@xxxxxxxxx>
Date: Thu, 21 Aug 2014 17:54:24 -0700
In-reply-to: <20140821210524.GG6343@eldon.alvh.no-ip.org>

Thank you for the guidance! So far so good with max_standby_archive/streaming_delay, no cancellations.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- hot_standby_feedback vs. max_standby_archive_delay/max_standby_streaming_delay?
  - From: Steve Kehlet
- Re: hot_standby_feedback vs. max_standby_archive_delay/max_standby_streaming_delay?
  - From: Alvaro Herrera

Prev by Date: Use of 'now' constant datatype in view to take advantage of partitioned table
Next by Date: SELECT 'NOW()' - OK, SELECT 'CLOCK_TIMESTAMP()' - ERROR
Previous by thread: Re: hot_standby_feedback vs. max_standby_archive_delay/max_standby_streaming_delay?
Next by thread: Use of 'now' constant datatype in view to take advantage of partitioned table
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux