Re: [HACKERS] RTE_NAMEDTUPLESTORE, enrtuples and comments - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] RTE_NAMEDTUPLESTORE, enrtuples and comments
Date
Msg-id 23683.1497369888@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] RTE_NAMEDTUPLESTORE, enrtuples and comments  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] RTE_NAMEDTUPLESTORE, enrtuples and comments
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Jun 13, 2017 at 11:53 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> But it needs to be changeable, unless you like the proposition that we
>> can never replan a query inside a trigger on the basis of new information
>> about how big the transition table is.  Even if you're okay with that
>> particular restriction, the NamedTupleStore stuff is supposed to be
>> flexible enough to accommodate other use-cases, and some of them will
>> surely not be okay with an immutable estimate for the store's size.

> Hmm, true.  But even if we extracted enrtuples from the
> RangeTbleEntry, there wouldn't be any mechanism to actually trigger
> such a replan, would there?

You're just pointing out that there's a lot of unfinished work around
this mechanism.  I don't think anybody has claimed otherwise.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] WIP: Data at rest encryption
Next
From: Julien Rouhaud
Date:
Subject: Re: [HACKERS] Typo in BRIN documentation