Re: Function modification visibility in parallel connection

From: Ivan Ivanov <m7onov(at)yandex(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Function modification visibility in parallel connection
Date: 2022-09-29 11:59:03
Message-ID: 98FED6D9-FBFE-4438-BE9E-18FD03FDC826@yandex.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> I wonder though if it could make sense to add AcceptInvalidationMessages
> to what StartTransactionCommand() does in the INPROGRESS cases. That
> would seem to bring things to parity with what happens for statements
> that aren't inside a transaction block, and the overhead wouldn't be
> very high (I think)

Thanks Tom!
Now I’m going to make a patch and suggest it to pgsql-hackers members as soon as I can.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2022-09-29 14:31:16 Re: BUG #17624: Creating database is non-ending execution.
Previous Message Glen Mailer 2022-09-29 08:50:50 Re: Possible bug with SKIP LOCKED behaviour