From: Tom Lane <tgl@sss.pgh.pa.us>
To: mark pether <mark.pether@gmail.com>
Cc: David Gould <daveg@sonic.net>
Cc: pgsql-bugs@postgresql.org
Subject: Re: BUG #14441: trim function bug (hit a keyword somewhere internally)
Date: Wed, 30 Nov 2016 01:51:36 -0500
Message-ID: <18216.1480488696@sss.pgh.pa.us> (raw)
In-Reply-To: <CAEnjbrTZ+GMF_XCV1r4Q42TLv3mR_EAeutUGTE8=Fn3nTrTxRw@mail.gmail.com>
References: <20161130011710.6539.53657@wrigleys.postgresql.org>
<20161129220932.123e13a1@engels>
<CAEnjbrTZ+GMF_XCV1r4Q42TLv3mR_EAeutUGTE8=Fn3nTrTxRw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>
mark pether <mark.pether@gmail.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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, mark.pether@gmail.com, daveg@sonic.net
Subject: Re: BUG #14441: trim function bug (hit a keyword somewhere internally)
In-Reply-To: <18216.1480488696@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox