From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Why overhead of SPI is so large? |
Date: | 2019-11-22 05:15:25 |
Message-ID: | CAFj8pRDjC9=jJ9mvK3ju8=YiErZJo4cxe5LfrkJjXVbdjM3m8w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
čt 21. 11. 2019 v 20:44 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> > čt 21. 11. 2019 v 10:31 odesílatel Konstantin Knizhnik <
> > k(dot)knizhnik(at)postgrespro(dot)ru> napsal:
> >> With contain_mutable_functions the patch becomes trivial.
>
> > Stable functions doesn't need own snapshot too, so it is not fully
> correct,
> > but it is on safe side.
>
> No, I doubt that. A stable function is allowed to inspect database state,
> and if it's being called by a volatile function, it has every right to
> expect that it'd see updates-so-far made by the volatile function.
>
for this I need new snapshot?
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2019-11-22 05:17:02 | Re: checkpointer: PANIC: could not fsync file: No such file or directory |
Previous Message | Pavel Stehule | 2019-11-22 05:11:32 | Re: obsolete example |