8 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link
7 replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
source | link
6 follow up questions
source | link

Follow-up questions:

  • Could I create a separate column of all three field concat'd or hashed for each table, and then index that column? Or is that what the composite GIN index is already doing?

  • Does casting play a role in slowing the query down? I notice in the EXPLAIN plan that the index is casting each field as ::text even though they are all varchar(256).

  • Alternative solutions: Would a columnar data store like Redshift be any more efficient at this? Does Redshift even have the ability to install extensions like pg_trgm? Are other fuzzy search tools better at this kind of multi-column searching (e.g. ElasticSearch)?

Follow-up questions:

  • Could I create a separate column of all three field concat'd or hashed for each table, and then index that column? Or is that what the composite GIN index is already doing?

  • Does casting play a role in slowing the query down? I notice in the EXPLAIN plan that the index is casting each field as ::text even though they are all varchar(256).

  • Alternative solutions: Would a columnar data store like Redshift be any more efficient at this? Does Redshift even have the ability to install extensions like pg_trgm? Are other fuzzy search tools better at this kind of multi-column searching (e.g. ElasticSearch)?

5 added 10 characters in body
source | link
4 added 786 characters in body
source | link
3 added 50 characters in body
source | link
2 added 100 characters in body
source | link
1
source | link