I have a question concerning the score. If i use an inner join i get a sql message saying : ERROR: ERREUR: la colonne « tableoid » n'existe pas
LINE 1: select f.fid_recherchefichiers, pgroonga_score(tableoid, cti...
^
HINT: Il existe une colonne nommée « tableoid » pour la table « p » mais elle ne peut pas être référencée dans cette partie de la requête.
SQL state: 42703
Character: 48
CREATE TABLE
, CREATE INDEX
, INSERT
, SELECT
, ...) to reproduce the case?
${PGDATA}/pgroonga.log
to the issue? pgroonga.log
will include the details for this case.
id, name
and around 3m records, which having name a pgroonga index. but the query doesn't use the index, it just performs a seq scan, is there any technique to enforce it?-- Table Definition ----------------------------------------------
CREATE TABLE datamarket.test_name (
id integer PRIMARY KEY,
name character varying
);
-- Indices -------------------------------------------------------
CREATE UNIQUE INDEX test_name_pkey ON datamarket.test_name(id int4_ops);
CREATE INDEX test_name_name_pgroonga ON datamarket.test_name(name pgroonga_text_full_text_search_ops_v2);
explain SELECT _default_.name AS name
FROM datamarket.test_name AS _default_
WHERE _default_.name &@ '欧莱雅' limit 10;
Limit (cost=10000000000.00..10000005192.86 rows=10 width=38)
-> Seq Scan on test_name _default_ (cost=10000000000.00..10001984712.56 rows=3822 width=38)
Filter: (name &@ '欧莱雅'::character varying)
-- this seems not working neither
set enable_seqscan = off;
show enable_seqscan; -- it does show off
I think, If the type of column is varchar, we need to specify to pgroonga_varchar_full_text_search_ops_v2
operator class.
For example, how about below example?
CREATE INDEX ${INDEX_NAME} ON ${TABLE_NAME} USING pgroonga (${COLUMN_NAME} pgroonga_varchar_full_text_search_ops_v2);
hi, we are experiencing a pg crash, which we suspect it may be pgroonga, we found a lot
6790878 2019-09-03 10:35:19.987139|n|11768: pgroonga: initialize: <2.2.1>
6790879 2019-09-03 10:35:19.989661|n|11654: io(base/23522/pgrn) collisions(1000/7): lock failed 1000 times
6790880 2019-09-03 10:35:20.039066|n|11664: io(base/23522/pgrn) collisions(1000/7): lock failed 1000 times
around crashing time
also, will pgroonga create tcp connections? we see the connections keep increasing
CREATE TABLE ...;
CREATE INDEX ...;
INSERT ...;
SELECT ...;