Re: PGroonga index-only scan problem with yesterday’s PostgreSQL updates - Mailing list pgsql-hackers

From Anders Kaseorg
Subject Re: PGroonga index-only scan problem with yesterday’s PostgreSQL updates
Date
Msg-id ae4cb0d2-c307-5a95-31ee-878d6f8deafd@mit.edu
Whole thread Raw
In response to Re: PGroonga index-only scan problem with yesterday’s PostgreSQL updates  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: PGroonga index-only scan problem with yesterday’s PostgreSQL updates
List pgsql-hackers
On 2/11/22 15:57, Tom Lane wrote:
> Possibly same issue I just fixed?
> 
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=e5691cc9170bcd6c684715c2755d919c5a16fea2

Yeah, that does seem to fix my test cases.  Thanks!

Any chance this will make it into minor releases sooner than three 
months from now?  I know extra minor releases are unusual, but this 
regression will be critical at least for self-hosted Zulip users and 
presumably other PGroonga users.

Anders



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pgsql: Add TAP test to automate the equivalent of check_guc
Next
From: Julien Rouhaud
Date:
Subject: Re: Replacing TAP test planning with done_testing()