David Johnston <david.g.johnston@xxxxxxxxx> writes: > â??While "planner hints" comes to mind...on the SQL side can we extend the > "PREPARE" command with two additional keywords?â?? > â??PREPARE > name [ ( data_type [, ...] ) ] [ > [NO] GENERIC > â??] â?? > â??AS statement Don't really see the point. The OP's problem is that the prepare is being driven by a client-side library, which would have even less clue than the backend as to whether a generic plan is more appropriate than a custom plan. The right thing here IMO is to improve the heuristics on the backend side. I'm sure we can do better, it's just going to take some thought. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
