From: | Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(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-12-01 00:50:12 |
Message-ID: | CAKU4AWoJyDRCruu7SzKw4NeDgHQ15ZxE_00pSgsFF4FA8LW3yw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 1, 2021 at 3:33 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> 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 think you misunderstand me, I argued with the answer because after I got
the
answer and I rethink my problem, I found my question description is not
accurate
enough, so I improved the question and willing discussion again. My
exception was
things will continue with something like this:
1. In your new described situation, your solution still does not work
because ...
2. In your new described situation, the solution would work for sure
3. your situation is still not cleared enough.
--
Best Regards
Andy Fan
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2021-12-01 00:54:18 | Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file |
Previous Message | Bossart, Nathan | 2021-12-01 00:49:43 | Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code) |