Re: vac_update_datfrozenxid will raise "wrong tuple length" if pg_database tuple contains toast attribute.

Arthur Nascimento <tureba@gmail.com>

From: Arthur Nascimento <tureba@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Ashwin Agrawal <ashwinstar@gmail.com>, Junfeng Yang <yjerome@vmware.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Ashwin Agrawal <aashwin@vmware.com>
Date: 2023-01-19T13:42:47Z
Lists: pgsql-hackers
Hi Michael,

I got a customer case that matches this issue. The customer is on an
old version of 12, but I see the patch only went into 14:

On Tue, 8 Dec 2020 at 00:32, Michael Paquier <michael@paquier.xyz> wrote:
> > Yes the attached patch looks good to me for PostgreSQL. Thanks Michael.
> Okay, committed to HEAD then.

commit 947789f1f5fb61daf663f26325cbe7cad8197d58
Author: Michael Paquier <michael@paquier.xyz>
Date:   Tue Dec 8 12:13:19 2020 +0900

   Avoid using tuple from syscache for update of pg_database.datfrozenxid

Would it be possible to backport the patch to 12 and 13?

-- 
Arthur Nascimento
EDB



Commits

  1. Avoid using tuple from syscache for update of pg_database.datfrozenxid