On Thu, Sep 7, 2017 at 1:16 AM, Robert Inder
wrote:
>
>
> On 6 September 2017 at 20:47, Jeff Janes wrote:
>
>>
>>> Have I misunderstood something? Or is Postgres not actually configured
>>> the way I think it is?
>>>
>>
>> The standby will wait for ten minutes to obtain the lock it wishes to
>>
On 6 September 2017 at 20:47, Jeff Janes wrote:
>
>> Have I misunderstood something? Or is Postgres not actually configured
>> the way I think it is?
>>
>
> The standby will wait for ten minutes to obtain the lock it wishes to
> obtain. In 9.4, if something other than dump of database b was alr
On Wed, Sep 6, 2017 at 9:43 AM, Robert Inder
wrote:
...
> And I've read that the answer to this is to set
> max_standby_streaming_delay in postgresql94.conf.
> So I've set it to "600s" -- ten minutes.
>
> I thought this would mean that when there was a conflict with an update
> from the live ser
A server running PostgreSQL 9.4 on Centos 6.8, with a live server and a hot
standby, is supporting about 20 customer organisations, each with their own
linux user and its own installation/copy of the system, talking to its own
database.
The system has a backup script which is a wrapper round pg_du
