Re: Update comments in multixact.c

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: "shiy(dot)fnst(at)fujitsu(dot)com" <shiy(dot)fnst(at)fujitsu(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Update comments in multixact.c
Date: 2023-01-24 23:18:10
Message-ID: CAH2-WzkFUZ0FOmurJ6nqfdw0g6HM+8qz3MvSo8jZwDcBTB7uwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 18, 2023 at 2:02 AM shiy(dot)fnst(at)fujitsu(dot)com
<shiy(dot)fnst(at)fujitsu(dot)com> wrote:
> Thanks for your reply.
>
> Attach a patch which fixed them.

Pushed something close to that just now. I decided that it was better
to not specify when truncation happened in these two places at all,
though. The important detail is that it can happen if certain rules
are not followed.

Thanks
--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2023-01-24 23:24:00 Re: Mutable CHECK constraints?
Previous Message Peter Geoghegan 2023-01-24 22:49:38 Re: New strategies for freezing, advancing relfrozenxid early