Re: Fix a Oracle-compatible instr function in the documentation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, nagata(at)sraoss(dot)co(dot)jp
Subject: Re: Fix a Oracle-compatible instr function in the documentation
Date: 2018-01-10 22:20:18
Message-ID: 28815.1515622818@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Evidently, they consider that negative beg_index indicates
> the last place where the target substring can *begin*, whereas
> our code thinks it is the last place where the target can *end*.

> After a bit of fooling around with it, I produced code that agrees
> with Oracle as far as I can tell, but it wouldn't be a bad idea
> for someone else to test it some more.

I spent some more time comparing this version's behavior with
rextester's Oracle instance, and couldn't find any other
discrepancies, so I pushed it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-01-10 22:21:54 Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)
Previous Message Peter Geoghegan 2018-01-10 22:05:30 Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)