On Tue, Jun 13, 2017 at 10:05 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Robert Haas <robertmh...@gmail.com> writes: >> Perhaps this is a silly question, but I don't particularly see what's >> wrong with: > >> 3. Do nothing. > > Well, the fundamental problem is that the RTE is a lousy place to keep > rowcount estimates. That breaks assorted desirable properties like > querytrees being readonly to planning/execution (not that we don't > end up copying them anyway, but up to now that's been because of bad > implementation not because the representation was broken by design).
How does it break those properties? I don't think enrtuples is being modified by planning or execution as things stand. -- 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
