Re: Drop database command will raise "wrong tuple length" if pg_database tuple contains toast attribute.

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
Cc: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Drop database command will raise "wrong tuple length" if pg_database tuple contains toast attribute.
Date: 2024-08-19 12:03:13
Message-ID: bd81049a-d0b2-4c0c-9475-9acd2e6efd15@vondra.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/19/24 12:16, Tomas Vondra wrote:
> On 8/19/24 11:01, Yugo Nagata wrote:
>
> ...
>
>> By the way, I found a comment in vac_update_datfrozenxid() and EventTriggerOnLogin()
>> that explains why we could not use tuples from the syscache for heap_inplace_update.
>> I think it is better ad d the same comment in dropdb(). I attached a trivial patch for it.
>>
>
> Agreed. That seems like a nice improvement to the comment.
>

Done, thanks for the suggestion / patch.

regards

--
Tomas Vondra

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-08-19 12:04:11 Re: gitmaster server problem?
Previous Message Alexander Lakhin 2024-08-19 12:00:00 Re: why is pg_upgrade's regression run so slow?