I pgroonga is found a bug in the replica db.
it is fine
will trigger ERROR: pgroonga: object isn't found: <Sources2813810>
when pgroonga.enable_wal = false
To fix the problem, add pgroonga.enable_wal = on in postgresql.conf and pg_ctl reload the slave db sever.
However, if pgroonga.enable_wal = on is kept, the slave pgroonga will cause postmaster crash and stop the service.
I need some help.
I am currently using MariaDB 10.1 and the full text search can't work with infix %..%
I am hoping Groonga (or MGroonga) can help me to achieve this limitation. Managed to install MGroonga inside MariaDB 10.1.
All my existing tables are InnoDB.
I did this
salesorder_mroonga engine=Mroonga select * from
managed to create the table successful.
So i add the fulltext index
alter table salesorder_mroonga add fulltext index pName (productName);
or using this way
salesorder_mroonga(fulltext index (productName)) engine=Mroonga select * from
Can add, but the fulltext index will show null for cardinality.
A fulltext index in InnoDB table salesorder will have 30,000 for cardinality.
So if I run this query, it will return 0.
select from salesorder_mroonga where match(productName) against ('Al*' in boolean mode);
Any idea why I add a fulltext index won't work?
You need to specify the
TokenBigramSplitSymbolAlphaDigit tokenizer (parser) when you create a full text index:
create table salesorder_mroonga(fulltext index (productName) parser "TokenBigramSplitSymbolAlphaDigit") engine=Mroonga
against('AI' in boolean mode)returns