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

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-hackers(at)postgresql(dot)org, 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:58:32
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> 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.


I agree with your commit message:

> Back-patch to all supported branches. Although this patch only touches
> documentation, we should probably call it out as a bug fix in the next
> minor release notes, since users who have adopted the functions will
> likely want to update their versions.

Best regards,
Tatsuo Ishii
SRA OSS, Inc. Japan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-01-10 22:59:08 Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)
Previous Message Daniel Gustafsson 2018-01-10 22:49:47 Re: [HACKERS] Refactoring identifier checks to consistently use strcmp