Re: insert and query performance on big string table with pg_trgm

Don't know if it would make PostgreSQL happier but how about adding a hash value column and creating the unique index on that one? May block some false duplicates but the unique index would be way smaller, speeding up inserts. 2017. nov. 25. 7:35 ezt írta ("Jeff Janes" ): >

Re: insert and query performance on big string table with pg_trgm

On Nov 21, 2017 00:05, "Matthew Hall" wrote: > Are all indexes present at the time you insert? It will probably be much faster to insert without the gin index (at least) and build it after the load. There is some flexibility on the initial load, but the updates in the

Re: insert and query performance on big string table with pg_trgm

Hi Jeff, Thanks so much for writing. You've got some great points. > On Nov 20, 2017, at 5:42 PM, Jeff Janes wrote: > While I have not done exhaustive testing, from the tests I have done I've > never found gist to be better than gin with trgm indexes. Thanks, this helps

insert and query performance on big string table with pg_trgm

Hello PGSQL experts, I've used your great database pretty heavily for the last 4 years, and during that time it's helped me to solve an amazingly wide variety of data challenges. Last week, I finally ran into something weird enough I couldn't figure it out by myself. I'm using a self-compiled