Stas Kelvich <s.kelv...@postgrespro.ru> writes:
> On 06 May 2016, at 00:46, Gavin Flower <gavinflo...@archidevsys.co.nz> wrote:
>> On 06/05/16 07:44, Tom Lane wrote:
>>> Yeah, I see we're already a bit inconsistent here. The problem with using
>>> a ts_ prefix, to my mind, is that it offers no option for distinguishing
>>> tsvector from tsquery, should you need to do that. Maybe this isn't a
>>> problem for functions that have tsvector as input.
>> use tsv_ and tsq_?
> That would be a good convention if we were able to easily rename old
> functions.
> But now that will just create another pattern on top of three existing (no
> prefix, ts_*, tsvector_*).
Yeah :-(. Well, time grows short, so let's go with ts_ for these.
I'll go make it happen.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
