Re: pg_restore_attribute_stats() accepts non-finite values

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ewan Young <kdbase(dot)hack(at)gmail(dot)com>
Cc: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)postgresql(dot)org>, Jan Nidzwetzki <jan(at)planetscale(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>
Subject: Re: pg_restore_attribute_stats() accepts non-finite values
Date: 2026-08-31 07:57:36
Message-ID: apUz8GXrL2b2o1jU@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 27, 2026 at 04:09:21PM +0800, Ewan Young wrote:
> Thanks for the thorough review, and for the history -- that context on why
> the checks were removed is helpful.

Question: do we get elog(ERROR) problems, assertion failures or
backend breakages when we insert these values or is the backend OK
with them?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2026-08-31 08:01:00 Re: Offline data checksum changes can cause incorrect checksum state on standbys
Previous Message Michael Paquier 2026-08-31 07:52:55 Re: [PATCH] Speed up pg_waldump TAP test and fix some GitHub CI Windows flakiness