On 21.01.2016 00:25, Alvaro Herrera wrote:
Artur Zakirov wrote:
I don't quite understand why aren't we using a custom GUC variable here.
These already have SHOW and SET support ...
Added GUC variables:
- pg_trgm.limit
- pg_trgm.substring_limit
I added this variables to the documentation.
show_limit() and set_limit() functions work correctly and they are marked as
deprecated.
Thanks. I'm willing to commit quickly a small patch that only changes
the existing function to GUCs, then have a look at a separate patch that
adds the new substring operator. Would you split the patch that way?
What status of this patch? In commitfest it is "Needs review".
Can this patch get the status "Ready for Commiter"?
--
Artur Zakirov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
