Re: [HACKERS] RTE_NAMEDTUPLESTORE, enrtuples and comments
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] RTE_NAMEDTUPLESTORE, enrtuples and comments |
Дата | |
Msg-id | 23683.1497369888@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] RTE_NAMEDTUPLESTORE, enrtuples and comments (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: [HACKERS] RTE_NAMEDTUPLESTORE, enrtuples and comments
|
Список | 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 по дате отправления: