On Tue, Apr 14, 2015 at 2:38 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > As I said, I'm still writing the first pieces of this so I'm not sure > what other ramifications it will have. If there are any thoughts, I > would appreciate them. (Particularly useful input on whether it is > acceptable to omit lognums/physnums from _outRangeTblEntry.)
I think the general rule is that an RTE should not contain any structure information about the underlying relation that can potentially change: the OID is OK because it's immutable for any given relation. The relkind is not quite immutable because you can create a _SELECT rule on a table and turn it into a view; I'm not sure how we handle that, but it's a fairly minor exception anyhow. Everything else in the RTE, with the new and perhaps-unfortunate exception of security quals, is stuff derived from what's in the query, not the table. I think it would be good for this to work the same way: the structural information about the table should be found in the relcache, not the RTE. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
