Alvaro Herrera <alvhe...@2ndquadrant.com> writes:
>> +
>> <entry><function>show_substring_limit()</function><indexterm><primary>show_substring_limit</primary></indexterm></entry>
>> +
>> <entry><function>set_substring_limit(real)</function><indexterm><primary>set_substring_limit</primary></indexterm></entry>
> I don't quite understand why aren't we using a custom GUC variable here.
Presumably this is following the existing set_limit() precedent
in pg_trgm. But I tend to agree that that's a crummy precedent
and we should not extend it.
Let's invent a custom GUC for the regular limit, mark show_limit()
and set_limit as deprecated, and then make just a custom GUC for
this other limit.
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
