Re: BUG #14441: trim function bug (hit a keyword somewhere internally)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: mark pether <mark(dot)pether(at)gmail(dot)com>
Cc: David Gould <daveg(at)sonic(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14441: trim function bug (hit a keyword somewhere internally)
Date: 2016-11-30 06:51:36
Message-ID: 18216.1480488696@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

mark pether <mark(dot)pether(at)gmail(dot)com> writes:
> Sorry, I misread the document it's not a bug, doco was unclear.
> It replaces the largest match which may be all characters or simply
> individual characters. I realised this after I created the bug.

Hmm, yeah, docs fail to make clear what happens with a multicharacter
trim spec. I think we could fix this with a better example.
Will do something about it.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Nikitin Nikolay 2016-11-30 08:36:51 Re: BUG #14438: Wrong row count in the join plan with unique index scan
Previous Message Tom Lane 2016-11-30 06:24:04 Re: BUG #14441: trim function bug (hit a keyword somewhere internally)