Thread: Slides for PGCon2016; "FTS is dead ? Long live FTS !"

 

 

On Thu, May 26, 2016 at 11:26 PM, Andreas Joseph Krogh <andreas@visena.com> wrote:

Hi.

 

Any news about when slides for $subject will be available?

 

I submitted slides to pgcon site, but it usually takes awhile, so you can download our presentation directly http://www.sai.msu.su/~megera/postgres/talks/pgcon-2016-fts.pdf
 

There are some missing features in rum index, but I hope we'll update github repository really soon.

--

Andreas Joseph Krogh

CTO / Partner - Visena AS

Mobile: +47 909 56 963

andreas@visena.com

www.visena.com

[snip]

 

I want to run 9.6 beta in production right now because of this:-)

 

wait-wait :)  We'd be happy to have feedback from production, of course, but please, wait a bit. We are adding support of sorting posting list/tree not by item pointer as in gin, but make use of additional information, for example, timestamp, which will provide additional speedup to the existing one.

--

Andreas Joseph Krogh

CTO / Partner - Visena AS

Mobile: +47 909 56 963

andreas@visena.com

www.visena.com

>> I submitted slides to pgcon site, but it usually takes awhile, so you can
>> download our presentation directly
>> http://www.sai.msu.su/~megera/postgres/talks/pgcon-2016-fts.pdf

Looking at slide 39 (attached) I get the impression that I
should be able to do the following:


- turn a coding system (say, ICD-10) into a dictionary
  by splitting the terms into single words

    say, "diabetes mellitus -> "diabetes", "mellitus"

- define stop words like "left", "right", ...

    say, "fracture left ulna" -> the "left" doesn't
    matter as far as coding is concerned

- also turn that coding system into queries by splitting
  the terms into single words, concatenating them
  with "&", and setting the ICD 10 code as tag on them

    say, "diabetes mellitus" -> "diabetes & mellitus [E11]"

- run an inverse FTS (FQS) against a user supplied string
  thereby finding queries (= tags = ICD10 codes) likely
  relevant to the input

    say, to_tsvector("patient was suspected to suffer from diabetes mellitus")
    -> tag = E11


Possible, not possible, insane, unintended use ?

Thanks,
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

On Sun, May 29, 2016 at 10:04 PM, Karsten Hilbert
<Karsten.Hilbert@gmx.net> wrote:
>>> I submitted slides to pgcon site, but it usually takes awhile, so you can
>>> download our presentation directly
>>> http://www.sai.msu.su/~megera/postgres/talks/pgcon-2016-fts.pdf
>
> Looking at slide 39 (attached) I get the impression that I
> should be able to do the following:
>
>
> - turn a coding system (say, ICD-10) into a dictionary
>   by splitting the terms into single words
>
>         say, "diabetes mellitus -> "diabetes", "mellitus"
>
> - define stop words like "left", "right", ...
>
>         say, "fracture left ulna" -> the "left" doesn't
>         matter as far as coding is concerned
>
> - also turn that coding system into queries by splitting
>   the terms into single words, concatenating them
>   with "&", and setting the ICD 10 code as tag on them
>
>         say, "diabetes mellitus" -> "diabetes & mellitus [E11]"
>
> - run an inverse FTS (FQS) against a user supplied string
>   thereby finding queries (= tags = ICD10 codes) likely
>   relevant to the input
>
>         say, to_tsvector("patient was suspected to suffer from diabetes mellitus")
>         -> tag = E11
>
>
> Possible, not possible, insane, unintended use ?

why not, it's the same kind of usage I used at slide #39.

create table icd10 (q tsquery, code text);
insert into icd10 values(to_tsquery('diabetes & mellitus'), '[E11]');
select * from icd10 where to_tsvector('patient was suspected to suffer
from diabetes mellitus') @@ q;
           q           | code
-----------------------+-------
 'diabet' & 'mellitus' | [E11]
(1 row)



>
> Thanks,
> Karsten
> --
> GPG key ID E4071346 @ eu.pool.sks-keyservers.net
> E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

 

 

On Sun, May 29, 2016 at 12:59 AM, Oleg Bartunov <obartunov@gmail.com> wrote:

 

 

On Thu, May 26, 2016 at 11:26 PM, Andreas Joseph Krogh <andreas@visena.com> wrote:

Hi.

 

Any news about when slides for $subject will be available?

 

I submitted slides to pgcon site, but it usually takes awhile, so you can download our presentation directly http://www.sai.msu.su/~megera/postgres/talks/pgcon-2016-fts.pdf
 

 

Please, download new version of slides. I added CREATE INDEX commands in examples.

--

Andreas Joseph Krogh

CTO / Partner - Visena AS

Mobile: +47 909 56 963

andreas@visena.com

www.visena.com

[snip]

He he, I reported 1st issue: https://github.com/postgrespro/rum/issues/1

 

Would be cool to see this fixed so I actually could have a sip of the rum:-)

 

It's not easy to fix this. We don't want rum depends on  btree_gin, so probably the easiest way is to have separate operator <=> in rum.

--

Andreas Joseph Krogh

CTO / Partner - Visena AS

Mobile: +47 909 56 963

andreas@visena.com

www.visena.com

On 2016-05-31 13:24, Stefan Keller wrote:
>
> > We chose RUM just because there are GIN and VODKA :)
> > But some people already suggested several meanings like Really
> Useful iMdex :)
> > We are open for suggestion.
>
> So I propose: "Ranking UMdex" ;-)
>

How about "Russian Unbelievable Magic"? Or just "RUssian Magic" if you
do believe...

/kaare