| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Subject: | Re: Can I assume relation would not be invalid during from ExecutorRun to ExecutorEnd |
| Date: | 2021-11-30 19:33:25 |
| Message-ID: | CA+TgmoYNP=3t4+u7aDbpcTEsak8Q09MdE84yYwNePMi6vi9igw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 30, 2021 at 4:47 AM Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> wrote:
>> my exception should be that the relcache should not be invalidated _after the first relation open_
>> in the executor (not the beginning of executorRun)。
>
> s/exception/expectation.
>
> To be more accurate, my expectation is for a single sql statement, after the first time I write data into
> the relation, until the statement is completed or "aborted and RelationClose is called in ResourceOwnerRelease",
> the relcache reset should never happen.
Well .... I'm not sure why you asked the question and then argued with
the answer you got. I mean, you can certainly decide how you think it
works, but that's not how I think it works.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-11-30 19:41:43 | Re: Rename dead_tuples to dead_items in vacuumlazy.c |
| Previous Message | Tomas Vondra | 2021-11-30 19:11:03 | Re: [PATCH] Don't block HOT update by BRIN index |