Re: BUG #13349: Recheck logic with index mixed up when used with LATERAL

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: lr(at)pcorp(dot)us, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13349: Recheck logic with index mixed up when used with LATERAL
Date: 2015-05-25 11:55:09
Message-ID: 55630D9D.3090508@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 05/25/2015 08:25 AM, lr(at)pcorp(dot)us wrote:
> The following bug has been logged on the website:
>
> Bug reference: 13349
> Logged by: Regina Obe
> Email address: lr(at)pcorp(dot)us
> PostgreSQL version: Unsupported/Unknown
> Operating system: Debian, Mingw-64 Postgresql 9.5 Recheck logic
> Description:
>
> We are finding issues in our PostGIS KNN distance recheck, and think the
> issue is with PostgreSQL since we can replicate with PostgreSQL built-in
> geometry types
>
> This issue only seems to happen if the LATERAL clause works against multiple
> records.

Thanks, fixed! I forgot to reset the new "reached end" flag when the
node is rescanned.

- Heikki

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message andrew 2015-05-25 14:26:57 BUG #13350: blindly fsyncing data dir considered harmful
Previous Message lr 2015-05-25 05:25:38 BUG #13349: Recheck logic with index mixed up when used with LATERAL