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

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Anders Kaseorg <andersk(at)mit(dot)edu>
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-16 14:00:05
Message-ID: e362e84a35ac6977c487236f12ad602faf7b2a04.camel@oopsware.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Am Montag, dem 14.02.2022 um 16:02 -0500 schrieb Andrew Dunstan:
> It occurred to me that this wasn't very well documented, so I created
> some docco:
> <
> https://wiki.postgresql.org/wiki/PostgreSQL_Buildfarm_Howto#Testing_Ad
> ditional_Software>

Thx Andrew, i wasn't aware of this, too! I'm going to use that for the
Informix FDW, since it has got rotten over the time a little and i'd
like to get some better code testing for it.

Bernd

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-02-16 14:25:40 Re: ICU for global collation
Previous Message Robert Haas 2022-02-16 13:41:30 Re: some aspects of our qsort might not be ideal