|From:||Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>|
|To:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Cc:||Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org|
|Subject:||Re: PATCH: Update snowball stemmers|
|Views:||Raw Message | Whole Thread | Download mbox|
On Fri, Jul 06, 2018 at 12:37:26PM -0400, Tom Lane wrote:
> > I don't know if we have a buildfarm animal testing Hungarian. Maybe we
> > need a buildfarm animal or two testing a large number of locales.
> I dunno that we need to set up a permanent buildfarm member for this.
> I had been thinking in terms of testing every available locale on my
> own machines before pushing, but given that the code is pretty static,
> do we need to do that repetitively?
I run installcheck for hu_HU.UTF-8, hu_HU.ISO-8859-2 and ru_RU.UTF-8
locales on laptop. Tests passed.
I think it is worth to consider that most text search functions
(to_tsvector, to_tsquery) use specific text search configuration (english
or a custom one). Only few of them use default text search configuration.
They are in json.sql, jsonb.sql, tsearch.sql tests.
Is it good idea to modify some current tests to use default configuration
or to add specific tests for locale testing?
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
|Next Message||Alvaro Herrera||2018-07-06 19:33:55||Re: documentation fixes for partition pruning, round three|
|Previous Message||Dave Cramer||2018-07-06 19:15:31||Re: pg_recvlogical use of SIGHUP|