"Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx> writes: > Robert Haas <robertmhaas@xxxxxxxxx> wrote: >> I don't know exactly what the right solution is off the top of my >> head, but digging in our heels is not it. > Well, I'm comfortable digging in my heels against doing *lame* hints > just because "it's what all the other kids are doing," which I think > is the only thing which would have satisfied the OP on this thread. Right. If someone comes up with a design that avoids the serious pitfalls of traditional hinting schemes, that'd be great. But I'm not interested in implementing Oracle-like hints just because Oracle has them, which I think was basically what the OP wanted. I haven't seen a hinting scheme that didn't suck (and that includes the aspects of our own current behavior that are hint-like). I don't say that there can't be one. I believe that the FAQ entry is meant to answer people who come along and say "oh, this is easily solved, just do what $PRODUCT does". The generic answer to that is "no, it's not that easy". But maybe the FAQ should be rephrased to be more like "we don't want traditional hints because of problems X, Y, and Z. If you have an idea that avoids those problems, let us know." regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
