Re: [bug fix] Cascading standby cannot catch up and get stuck emitting the same message repeatedly - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject Re: [bug fix] Cascading standby cannot catch up and get stuck emitting the same message repeatedly
Date
Msg-id 0A3221C70F24FB45833433255569204D1F64039E@G01JPEXMBYT05
Whole thread Raw
In response to Re: [bug fix] Cascading standby cannot catch up and get stuck emitting the same message repeatedly  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [bug fix] Cascading standby cannot catch up and get stuck emitting the same message repeatedly
List pgsql-hackers
From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Amit Kapila
> It looks like the code in 9.3 or later version uses the recptr as the target
> segment location
> (targetSegmentPtr) whereas 9.2 uses recptr as beginning of segment (readOff
> = 0;).  If above understanding is right then it will set different values
> for latestPagePtr in 9.2 and 9.3 onwards code.
> 

In 9.2, the relevant variable is not recptr but recaddr.  recaddr in 9.2 and recptr in later releases point to the
beginningof a page just read, which is not always the beginning of the segment (targetSegmentPtr).
 

Regards
Takayuki Tsunakawa


pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Pinning a buffer in TupleTableSlot is unnecessary
Next
From: Tom Lane
Date:
Subject: Re: Adding the optional clause 'AS' in CREATE TRIGGER