From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexey Bashtanov <bashtanov@imap.cc>
cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Less-silly selectivity for JSONB matching operators
In-reply-to: <8fcbdcc5-cbed-f96f-7ed4-f34d1bd1a205@imap.cc>
References: <12237.1582833074@sss.pgh.pa.us> <14469.1582927774@sss.pgh.pa.us>
 <8fcbdcc5-cbed-f96f-7ed4-f34d1bd1a205@imap.cc>
Comments: In-reply-to Alexey Bashtanov <bashtanov@imap.cc>
	message dated "Tue, 31 Mar 2020 16:55:13 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9232.1585671632.1@sss.pgh.pa.us>
Date: Tue, 31 Mar 2020 12:20:32 -0400
Message-ID: <9233.1585671632@sss.pgh.pa.us>
Precedence: bulk

Alexey Bashtanov <bashtanov@imap.cc> writes:
> The only little thing I can think of is hardcoding it as 2 * DEFAULT_EQ_SEL.
> While I don't have any arguments against the value itself I think it 
> should be configurable independently.
> Sadly DEFAULT_MATCH_SEL name is already taken for text patterns.
> Not sure if it's a reason to rename all the stuff.

Yeah, I was going to invent a symbol till I noticed that DEFAULT_MATCH_SEL
was already taken :-(.

There are only about half a dozen uses of that in-core, so maybe we could
get away with renaming that one, but on the whole I'd rather leave it
alone in case some extension is using it.  So that leaves us with needing
to find a better name for this new one.  Any ideas?

			regards, tom lane