Re: Assertion failure in HEAD and 13 after calling COMMIT in a stored proc - Mailing list pgsql-hackers

From Ranier Vilela
Subject Re: Assertion failure in HEAD and 13 after calling COMMIT in a stored proc
Date
Msg-id CAEudQArab1xw9_GvzjTLkxKxdeV+utdHruY5LQ-Cw6VfoM=_9g@mail.gmail.com
Whole thread Raw
In response to Re: Assertion failure in HEAD and 13 after calling COMMIT in a stored proc  (Greg Nancarrow <gregn4422@gmail.com>)
List pgsql-hackers
Em qua., 23 de jun. de 2021 às 21:45, Greg Nancarrow <gregn4422@gmail.com> escreveu:
On Wed, Jun 23, 2021 at 11:01 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
>
> The code is correct as-is; the proposed change would result in taking
> more snapshots than needed.  Perhaps the comment needs revision, since
> you both misread it.  The comment is written in terms of "when can we
> skip taking a snapshot", while the test in the code is written for
> the inverse condition "when do we need a snapshot".

Yes, you're right.
Even though I did realise that the comment was talking about the
inverse, the condition for needing a snapshot still seemed too narrow,
based on the comment, but checking the cases again, it is correct.
I still don't agree. But we leave the code like that, to see how it behaves. 


Perhaps that code could have been written as the following, to better
align with the comments:

    skip_snapshot = (!expr->expr_simple_mutable || estate->readonly_func);
    if (!skip_snapshot)
    {
        ...
    }

    ...

    if (!skip_snapshot)
        PopActiveSnapshot();
-1. That way it's readability is much worse, more complicated and IMHO it generates worse asm.

regards,
Ranier Vilela

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: [Patch] change the default value of shared_buffers in postgresql.conf.sample
Next
From: Ranier Vilela
Date:
Subject: Re: Assertion failure in HEAD and 13 after calling COMMIT in a stored proc