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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: 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-14 21:02:37
Message-ID: 9c72ce16-3a2b-2347-3a02-7f1b257cbb72@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2/12/22 12:25, Tom Lane wrote:
>
> An even slicker answer would be to set up a PG buildfarm machine
> that, in addition to the basic tests, builds PGroonga against the
> new PG sources and runs your tests. Andrew's machine "crake" does
> that for RedisFDW and BlackholeFDW, and the source code for at least
> the latter module is in the buildfarm client distribution.

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_Additional_Software>

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-02-14 21:18:04 pgsql: Move scanint8() to numutils.c
Previous Message Tom Lane 2022-02-14 20:48:12 Re: Time to drop plpython2?