PostgreSQL Reversed ILIKE on column name












0















I am trying to figure out the given username by frontend is a valid name or not.
I have a table that contains lot of names.
So for example I got Adam18 I need to give an answer in real time (< 500ms)



My query:



SELECT * FROM names WHERE 'Adam18' ILIKE '%' || name || '%'


The query is correct but it uses sequential scan



Explain result:



Seq Scan on names  (cost=0.00..2341.20 rows=527 width=516) (actual time=1.452..24.774 rows=12 loops=1)
Filter: ('Adam18'::text ~~ (('%'::text || (name)::text) || '%'::text))
Rows Removed by Filter: 105314
Buffers: shared hit=498
Planning time: 0.062 ms
Execution time: 24.796 ms


Is there a way to create index on this case?



My current index:



CREATE INDEX names_gin_idx ON names USING gin (name gin_trgm_ops)


I cannot use this. Can you help me?










share|improve this question

























  • Yes I did it, there are 105 326 rows in the table

    – L.Farkas
    Nov 22 '18 at 13:35













  • Those 24ms are already way below the required 500ms ;) But I think trigram indexes can only be used in the "other directory", e.g. where name ilike '%Adam18%' Full text search might be an alternative

    – a_horse_with_no_name
    Nov 22 '18 at 13:54











  • I guess its faster now than I tried first time, because of the cache. What kind of index do you suggest on ILike instead of full text search?

    – L.Farkas
    Nov 22 '18 at 14:02











  • As I said: I don't think you can support that condition with an index (only the "other way round")

    – a_horse_with_no_name
    Nov 22 '18 at 14:04
















0















I am trying to figure out the given username by frontend is a valid name or not.
I have a table that contains lot of names.
So for example I got Adam18 I need to give an answer in real time (< 500ms)



My query:



SELECT * FROM names WHERE 'Adam18' ILIKE '%' || name || '%'


The query is correct but it uses sequential scan



Explain result:



Seq Scan on names  (cost=0.00..2341.20 rows=527 width=516) (actual time=1.452..24.774 rows=12 loops=1)
Filter: ('Adam18'::text ~~ (('%'::text || (name)::text) || '%'::text))
Rows Removed by Filter: 105314
Buffers: shared hit=498
Planning time: 0.062 ms
Execution time: 24.796 ms


Is there a way to create index on this case?



My current index:



CREATE INDEX names_gin_idx ON names USING gin (name gin_trgm_ops)


I cannot use this. Can you help me?










share|improve this question

























  • Yes I did it, there are 105 326 rows in the table

    – L.Farkas
    Nov 22 '18 at 13:35













  • Those 24ms are already way below the required 500ms ;) But I think trigram indexes can only be used in the "other directory", e.g. where name ilike '%Adam18%' Full text search might be an alternative

    – a_horse_with_no_name
    Nov 22 '18 at 13:54











  • I guess its faster now than I tried first time, because of the cache. What kind of index do you suggest on ILike instead of full text search?

    – L.Farkas
    Nov 22 '18 at 14:02











  • As I said: I don't think you can support that condition with an index (only the "other way round")

    – a_horse_with_no_name
    Nov 22 '18 at 14:04














0












0








0








I am trying to figure out the given username by frontend is a valid name or not.
I have a table that contains lot of names.
So for example I got Adam18 I need to give an answer in real time (< 500ms)



My query:



SELECT * FROM names WHERE 'Adam18' ILIKE '%' || name || '%'


The query is correct but it uses sequential scan



Explain result:



Seq Scan on names  (cost=0.00..2341.20 rows=527 width=516) (actual time=1.452..24.774 rows=12 loops=1)
Filter: ('Adam18'::text ~~ (('%'::text || (name)::text) || '%'::text))
Rows Removed by Filter: 105314
Buffers: shared hit=498
Planning time: 0.062 ms
Execution time: 24.796 ms


Is there a way to create index on this case?



My current index:



CREATE INDEX names_gin_idx ON names USING gin (name gin_trgm_ops)


I cannot use this. Can you help me?










share|improve this question
















I am trying to figure out the given username by frontend is a valid name or not.
I have a table that contains lot of names.
So for example I got Adam18 I need to give an answer in real time (< 500ms)



My query:



SELECT * FROM names WHERE 'Adam18' ILIKE '%' || name || '%'


The query is correct but it uses sequential scan



Explain result:



Seq Scan on names  (cost=0.00..2341.20 rows=527 width=516) (actual time=1.452..24.774 rows=12 loops=1)
Filter: ('Adam18'::text ~~ (('%'::text || (name)::text) || '%'::text))
Rows Removed by Filter: 105314
Buffers: shared hit=498
Planning time: 0.062 ms
Execution time: 24.796 ms


Is there a way to create index on this case?



My current index:



CREATE INDEX names_gin_idx ON names USING gin (name gin_trgm_ops)


I cannot use this. Can you help me?







database postgresql indexing query-optimization sql-like






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 '18 at 13:34







L.Farkas

















asked Nov 22 '18 at 13:28









L.FarkasL.Farkas

84




84













  • Yes I did it, there are 105 326 rows in the table

    – L.Farkas
    Nov 22 '18 at 13:35













  • Those 24ms are already way below the required 500ms ;) But I think trigram indexes can only be used in the "other directory", e.g. where name ilike '%Adam18%' Full text search might be an alternative

    – a_horse_with_no_name
    Nov 22 '18 at 13:54











  • I guess its faster now than I tried first time, because of the cache. What kind of index do you suggest on ILike instead of full text search?

    – L.Farkas
    Nov 22 '18 at 14:02











  • As I said: I don't think you can support that condition with an index (only the "other way round")

    – a_horse_with_no_name
    Nov 22 '18 at 14:04



















  • Yes I did it, there are 105 326 rows in the table

    – L.Farkas
    Nov 22 '18 at 13:35













  • Those 24ms are already way below the required 500ms ;) But I think trigram indexes can only be used in the "other directory", e.g. where name ilike '%Adam18%' Full text search might be an alternative

    – a_horse_with_no_name
    Nov 22 '18 at 13:54











  • I guess its faster now than I tried first time, because of the cache. What kind of index do you suggest on ILike instead of full text search?

    – L.Farkas
    Nov 22 '18 at 14:02











  • As I said: I don't think you can support that condition with an index (only the "other way round")

    – a_horse_with_no_name
    Nov 22 '18 at 14:04

















Yes I did it, there are 105 326 rows in the table

– L.Farkas
Nov 22 '18 at 13:35







Yes I did it, there are 105 326 rows in the table

– L.Farkas
Nov 22 '18 at 13:35















Those 24ms are already way below the required 500ms ;) But I think trigram indexes can only be used in the "other directory", e.g. where name ilike '%Adam18%' Full text search might be an alternative

– a_horse_with_no_name
Nov 22 '18 at 13:54





Those 24ms are already way below the required 500ms ;) But I think trigram indexes can only be used in the "other directory", e.g. where name ilike '%Adam18%' Full text search might be an alternative

– a_horse_with_no_name
Nov 22 '18 at 13:54













I guess its faster now than I tried first time, because of the cache. What kind of index do you suggest on ILike instead of full text search?

– L.Farkas
Nov 22 '18 at 14:02





I guess its faster now than I tried first time, because of the cache. What kind of index do you suggest on ILike instead of full text search?

– L.Farkas
Nov 22 '18 at 14:02













As I said: I don't think you can support that condition with an index (only the "other way round")

– a_horse_with_no_name
Nov 22 '18 at 14:04





As I said: I don't think you can support that condition with an index (only the "other way round")

– a_horse_with_no_name
Nov 22 '18 at 14:04












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432058%2fpostgresql-reversed-ilike-on-column-name%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432058%2fpostgresql-reversed-ilike-on-column-name%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Alcedinidae

RAC Tourist Trophy