| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, Tomas Vondra <tomas(at)vondra(dot)me>, pgsql-hackers(at)lists(dot)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Subject: | Re: Extended Statistics set/restore/clear functions. |
| Date: | 2025-11-23 06:57:31 |
| Message-ID: | aSKwW00LiORNNoxC@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Nov 22, 2025 at 03:26:19AM -0500, Corey Huinker wrote:
> I'm open to it, but there was significant pushback to having tight validity
> checks on other stats types.
Yeah, I am not sure that there is much value in having strict checks
for the values. Some control over the arguments listed in a single
object is much more valuable as these are easy to check in the input
functions.
> The more things that we make errors, the more chances we have to breaking a
> dump/restore. Granted, such values should never happen, but odd things do
> happen.
Indeed. Like the existing import functions, these should not lead to
hard failures, but WARNING-level reports.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Corey Huinker | 2025-11-23 07:27:49 | Re: Import Statistics in postgres_fdw before resorting to sampling. |
| Previous Message | sunil s | 2025-11-23 06:42:23 | Re: Unnecessary delay in streaming replication due to replay lag |