Re: Accept invalidation messages before the query starts inside a transaction

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Andrei Lepikhov <lepihov(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Accept invalidation messages before the query starts inside a transaction
Date: 2024-09-12 06:31:01
Message-ID: CAKFQuwYbDPg8-+iU-7kBk39juXbQ-1taAKLFSSzb2uGRimbBxw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday, September 11, 2024, Andrei Lepikhov <lepihov(at)gmail(dot)com> wrote:
>
>
> I don't know whether to classify this as a bug.
>
> [1] https://www.postgresql.org/docs/16/mvcc-caveats.html
>
>
Seems we need to add another sentence to that final paragraph. Something
like:

However, once an object is accessed within a transaction its definition is
cached for the duration of the transaction. Of particular note are routine
bodies modified using create or replace. If a replacement gets committed
mid-transaction the old code body will still be executed for the remainder
of the transaction.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hunaid Sohail 2024-09-12 07:44:23 Re: [PATCH] Add roman support for to_number function
Previous Message Nazir Bilal Yavuz 2024-09-12 06:10:44 Re: Avoid dead code (contrib/pg_visibility/pg_visibility.c)