Re: Sudden FTS-related error from parallel worker in 9.6

Поиск
Список
Период
Сортировка
От Devrim Gündüz
Тема Re: Sudden FTS-related error from parallel worker in 9.6
Дата
Msg-id 1475559450.7078.24.camel@gunduz.org
обсуждение исходный текст
Ответ на Re: Sudden FTS-related error from parallel worker in 9.6  (Nikolay Samokhvalov <samokhvalov@gmail.com>)
Ответы Re: Sudden FTS-related error from parallel worker in 9.6  (Nikolay Samokhvalov <samokhvalov@gmail.com>)
Список pgsql-bugs
Hi,

On Tue, 2016-10-04 at 08:13 +0300, Nikolay Samokhvalov wrote:
> No. It's valid for my instance.
> I have manually created configuration called 'ru'. But not in the databases
> 'test'.

I am not 100% familiar with this, but IIRC you need to create this in that
database, too.

I first created the tables as you did, and then:

postgres=# SELECT version();                                                version
            
---------------------------------------------------------------------------------------------------------PostgreSQL
9.6.0on x86_64-pc-linux-gnu, compiled by gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2), 64-bit 
(1 row)

postgres=# CREATE TEXT SEARCH CONFIGURATION ru (COPY=russian);
CREATE TEXT SEARCH CONFIGURATION
postgres=# EXPLAIN ANALYZE SELECT min(ts) FROM test;                                                  QUERY PLAN
                                            

-----------------------------------------------------------------------------------------------------------------Aggregate
(cost=2266.00..2266.01 rows=1 width=8) (actual time=15.740..15.740 rows=1 loops=1)  ->  Seq Scan on test
(cost=0.00..2016.00rows=100000 width=8) (actual time=0.006..8.032 rows=100000 loops=1)Planning time: 0.212 msExecution
time:15.782 ms 
(4 rows)

postgres=# SET default_text_search_config TO ru;
SET
postgres=# EXPLAIN ANALYZE SELECT min(ts) FROM test;                                                  QUERY PLAN
                                            

-----------------------------------------------------------------------------------------------------------------Aggregate
(cost=2266.00..2266.01 rows=1 width=8) (actual time=13.292..13.293 rows=1 loops=1)  ->  Seq Scan on test
(cost=0.00..2016.00rows=100000 width=8) (actual time=0.009..6.572 rows=100000 loops=1)Planning time: 0.069 msExecution
time:13.317 ms 
(4 rows)

postgres=# SET max_parallel_workers_per_gather TO 8;
SET
postgres=# EXPLAIN ANALYZE SELECT min(ts) FROM test;                                                  QUERY PLAN
                                            

-----------------------------------------------------------------------------------------------------------------Aggregate
(cost=2266.00..2266.01 rows=1 width=8) (actual time=13.701..13.701 rows=1 loops=1)  ->  Seq Scan on test
(cost=0.00..2016.00rows=100000 width=8) (actual time=0.009..6.882 rows=100000 loops=1)Planning time: 0.063 msExecution
time:13.722 ms 
(4 rows)

postgres=# \c test
You are now connected to database "test" as user "postgres".
test=# SET default_text_search_config TO ru;
ERROR:  invalid value for parameter "default_text_search_config": "ru"


-HTH
--
Devrim GÜNDÜZ
EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: BUG #14319: Logical decoding dropping statements in subtransactions
Следующее
От: Nikolay Samokhvalov
Дата:
Сообщение: Re: Sudden FTS-related error from parallel worker in 9.6