Re: When Update balloons memory
От | Peter Geoghegan |
---|---|
Тема | Re: When Update balloons memory |
Дата | |
Msg-id | CAH2-WznKE7uFnXRGw+U0DpXcmho0_s6Otd9dqGTcOnsvqJMZyA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: When Update balloons memory (Peter Geoghegan <pg@bowt.ie>) |
Ответы |
Re: When Update balloons memory
|
Список | pgsql-bugs |
On Tue, Jan 11, 2022 at 11:59 AM Peter Geoghegan <pg@bowt.ie> wrote: > On Tue, Jan 11, 2022 at 11:54 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Pass NULL for that, per 6867f963e: > > > > https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=6867f963e#patch2 > > Will look into that. Took a look. Not sure that using pull_varnos would represent an improvement, though. Do you feel strongly about it? The current approach has the advantage of allowing index_expression_changed_walker to directly apply an FirstLowInvalidHeapAttributeNumber offset to each Var's varattno. We can't just use bms_overlap to check for overlap between the bms returned by pull_varnos and our updatedColumns bms. It would be possible to transform the bms returned by pull_varnos to compensate, of course, but that seems rather awkward -- Peter Geoghegan
В списке pgsql-bugs по дате отправления: