On Fri, Jan 18, 2013 at 12:32 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> Makes sense?
Yes. The catalog timetravel stuff still gives me heartburn. The idea
of treating system catalogs in a special way has never sat well with
me and still doesn't - not that I am sure what I'd like better. The
complexity of the whole system is also somewhat daunting.
But my question with relation to this specific patch was mostly
whether setting the table OID everywhere was worth worrying about from
a performance standpoint, or whether any of the other adjustments this
patch makes could have negative consequences there, since the
Satisfies functions can get very hot on some workloads. It seems like
the consensus is "no, that's not worth worrying about", at least as
far as the table OIDs are concerned.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
