On Mon, Mar 16, 2015 at 2:55 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Robert Haas <robertmh...@gmail.com> writes: >> Is there a reason not to make a rule that opclass members must be >> parallel-safe? I ask because I think it's important that the process >> of planning a query be categorically parallel-safe. > > I'm not seeing the connection between those two statements. The planner > doesn't usually execute opclass members, at least not as such.
Hmm, I guess I'm spouting nonsense there. The way the operator gets invoked during planning is that eqsel() calls it. But that doesn't require it to be part of an opclass; it just has to be an operator that's chosen that eqsel as its selectivity estimator. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers