| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, 125atishprak(at)gmail(dot)com |
| Subject: | Re: BUG #19857: Stats restore rejects empty arrays, losing range and array stats |
| Date: | 2026-11-11 22:40:47 |
| Message-ID: | avTu757_g0z96QA2@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Nov 11, 2026 at 08:46:56AM -0500, Corey Huinker wrote:
> Nitpick: I think the error message itself needs to change based on
> allow_empty, as true allows 1-D or empty, and false allows only 1-D.
Yeah, point taken that this could be a little bit better, in a shape
similar to what you are suggesting. I can see that we have similar
requirements in some of the array functions, though.. Will try to
shape that this way.
> This way seems not invasive at all, so I like it better.
Okay, noted.
> I'll redo the ext stats patchset to this pattern. Do you intend to commit
> this soon? Asking so I know whether to rebase-away the 0001 patch.
Yeah, I intend to wrap this one this morning.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2026-11-12 01:23:15 | Re: BUG #19625: SQL/JSON boolean DEFAULT expression silently replaced with 'false' |
| Previous Message | Michael Paquier | 2026-11-11 22:34:18 | Re: BUG #19849: queries fail after ANALYZE with expression stats on arrays |