| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Recovery inconsistencies, standby much larger than primary |
| Date: | 2014-02-14 00:39:04 |
| Message-ID: | 31995.1392338344@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark <stark(at)mit(dot)edu> writes:
> On Thu, Feb 13, 2014 at 7:52 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> That's what's bothering me, too. On the other hand, if we can't think of
>> a scenario where it'd be necessary to replay the high-offset update, then
>> I'm disinclined to mess with the code further.
> And the whole point of the undefined page error checking is to detect
> cases like this, so covering them up in the name of possible edge
> cases we haven't thought of kind of defeats the purpose.
Yeah, good point. Let's leave it alone and see if the existing fix
helps.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabrízio de Royes Mello | 2014-02-14 00:44:56 | Re: [PATCH] Store Extension Options |
| Previous Message | Andres Freund | 2014-02-13 23:53:43 | Re: issue with gininsert under very high load |