Re: v12.0 ERROR: trying to store a heap tuple into wrong type of slot

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: v12.0 ERROR: trying to store a heap tuple into wrong type of slot
Date: 2019-10-15 22:26:59
Message-ID: 20191015222658.GT3599@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 15, 2019 at 01:50:09PM -0700, Andres Freund wrote:
> On 2019-10-13 07:51:06 -0700, Andres Freund wrote:
> > On 2019-10-11 16:03:20 -0500, Justin Pryzby wrote:
> > > ts=# CLUSTER huawei_m2000_config_enodebcell_enodeb USING huawei_m2000_config_enodebcell_enodeb_coalesce_idx ;
> > The cause of the error is that, while that sounds like it should be the
> > case, a virtual slot isn't sufficient for tuplesort_begin_cluster(). So
> > the fix is pretty trivial. Will fix.
>
> I pushed the fix, including a few tests, a few hours ago. I hope that
> fixes the issue for you?

On another server already running REL_12_STABLE, I created index with same
definition, which didn't previously exist. I failed before pulling and
works after.

ts=# CLUSTER huawei_m2000_config_enodebcell_enodeb USING huawei_m2000_config_enodebcell_enodeb_coalesce_idx ;
CLUSTER

Thanks,
Justin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2019-10-15 22:40:47 Re: BRIN index which is much faster never chosen by planner
Previous Message Andres Freund 2019-10-15 20:50:09 Re: v12.0 ERROR: trying to store a heap tuple into wrong type of slot