Re: PGroonga index-only scan problem with yesterday’s PostgreSQL updates

From: Anders Kaseorg <andersk(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Sutou Kouhei <kou(at)clear-code(dot)com>
Subject: Re: PGroonga index-only scan problem with yesterday’s PostgreSQL updates
Date: 2022-02-12 00:51:53
Message-ID: ae4cb0d2-c307-5a95-31ee-878d6f8deafd@mit.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2022-02-12 02:06:03 Re: Replacing TAP test planning with done_testing()
Previous Message Michael Paquier 2022-02-12 00:49:47 Re: pgsql: Add TAP test to automate the equivalent of check_guc