Re: Another unexpected behaviour

Thanks. That's the best reason I can think of too.

"Less expensive" feels like taking shortcuts to speed up things and not a
good reason to make decision on.
Although maintain backward compatibility makes sense (to some extend), if
old PG doesn't behave properly, it should be fixed, shouldn't it?



--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Another-unexpected-behaviour-tp4610242p4616513.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.