| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
| Cc: | Hiroyuki Sato <hiroysato(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: grep -f keyword data query |
| Date: | 2015-12-27 18:38:56 |
| Message-ID: | 2978.1451241536@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> writes:
>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> hat am 27. Dezember 2015 um 19:11 geschrieben:
>> What in the world is this @~ operator? And what sort of index are
>> you using now, that can accept it? Are the rowcount estimates in
>> the EXPLAIN output accurate? (If they are, it's hardly surprising
>> that the query takes a long time.)
> in a privat mail he called an other operator: ~~. I think, the @~ is an error.
Well, ~~ isn't directly indexable by btree indexes either, so there's
still something wrong with either the EXPLAIN output or the claimed
index definitions.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melvin Davidson | 2015-12-27 18:55:30 | Re: Calling function (table_name, schema_name) within event trigger |
| Previous Message | Susan Hurst | 2015-12-27 18:27:57 | Calling function (table_name, schema_name) within event trigger |