On Tue, Dec 10, 2013 at 3:08 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> So my objection to what Peter is suggesting is not that it's a bad idea
> in isolation, but that I don't see where he's going to stop, short of
> reinventing every query-normalization behavior that exists in the planner.
> If this particular case is worthy of fixing with a hack in the
> fingerprinter, aren't there going to be dozens more with just as good
> claims? (Perhaps not, but what's the basis for thinking this is far
> worse than any other normalization issue?)
Qualitatively, the dynamic length values list is the worst offender.
There is no algebraic solution to where to stop with normalizations,
but as Peter points out, that bridge has been crossed already:
assumptions have already been made that toss some potentially useful
information already, and yet the program is undoubtedly practical.
Based on my own experience (which sounds similar to Andres's), I am
completely convinced the canonicalization he proposes here is more
practical than the current definition to a large degree, so I suggest
the goal is worthwhile.
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: