Postgres Pro
Downloads
Home   >   mailing lists

Re: Hot standby and b-tree killed items - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Hot standby and b-tree killed items
Date
Msg-id 494BA5DE.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to Re: Hot standby and b-tree killed items  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Hot standby and b-tree killed items  (Simon Riggs <simon@2ndQuadrant.com>)
Re: Hot standby and b-tree killed items  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Tree view 
>>> Simon Riggs <simon@2ndQuadrant.com> wrote: 
> max_standby_delay is set in recovery.conf, value 0 (forever) -
2,000,000
> secs, settable in milliseconds. So think of it like a deadlock
detector
> for recovery apply.
Aha!  A deadlock is a type of serialization failure.  (In fact, on
databases with lock-based concurrency control rather than MVCC, it can
be the ONLY type of serialization failure.)
-Kevin

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot standby and b-tree killed items
Next
From: Tom Lane
Date:
Subject: Re: Windowing Function Patch Review -> Standard Conformance