Re: [COMMITTERS] pgsql: Remove secondary checkpoint

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Andreas Seltenreich <seltenreich(at)gmx(dot)de>, pgsql-committers <pgsql-committers(at)postgresql(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Subject: Re: [COMMITTERS] pgsql: Remove secondary checkpoint
Date: 2017-11-20 20:50:40
Message-ID: CANP8+jK_MsDa8dFV5wO3=U2V6b3oHzQ55D5nqd-o9Yu31r-rGQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 20 November 2017 at 08:38, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Sat, Nov 11, 2017 at 10:58 PM, Andreas Seltenreich
> <seltenreich(at)gmx(dot)de> wrote:
>> Hi,
>>
>> sqlsmith doesn't like commit 4b0d28de06:
>>
>> ,----
>> | regression=> select * from pg_control_checkpoint();
>> | server closed the connection unexpectedly
>> | TRAP: FailedAssertion("!((atti->attalign) == 's')", File: "heaptuple.c", Line: 126)
>> `----
>>
>> On a build with assertions disabled, the statement fails with an error
>> instead:
>>
>> ,----
>> | regression=> select * from pg_control_checkpoint();
>> | ERROR: function return row and query-specified return row do not match
>> | DETAIL: Returned row contains 19 attributes, but query expects 18.
>> `----
>>
>> The attached patch fixes it for me.
>>
>
>
> Your patch looks correct to me. I can reproduce the problem and
> verified that patch fixes the problem. It is better to track this in
> CF if not already tracked.

What email and patch is this referring to?

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2017-11-20 20:55:04 Re: [COMMITTERS] pgsql: Remove secondary checkpoint
Previous Message Andres Freund 2017-11-20 19:18:45 Re: [HACKERS] [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple