| From: | Ayoub Kazar <ayoub(dot)kazar(at)data-bene(dot)io> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: file_fdw: Fix ANALYZE does not enforce REJECT_LIMIT with on_error 'ignore' |
| Date: | 2026-11-05 19:07:10 |
| Message-ID: | 7663f95c-7f90-45a9-a618-a6906edaab39@data-bene.io |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/11/2026 16:24, Fujii Masao wrote:
> On Thu, Nov 5, 2026 at 9:40 AM Ayoub Kazar <ayoub(dot)kazar(at)data-bene(dot)io> wrote:
>> However, ANALYZE silently ignores reject_limit, skips all
>> malformed rows, and finishes with a NOTICE.
> Personally, I'd prefer to keep this behavior. Statistics based on valid rows
> are still useful even when the number of errors exceeds reject_limit.
> Queries may still succeed, for example, when using LIMIT, whereas
> aborting ANALYZE would leave the statistics outdated. So I think
> ANALYZE should continue to ignore reject_limit. Thought?
Yes, very reasonable.
The NOTICE itself also provides good info about what's going on, so
that's okay.
>
> If we agree, how about documenting this exception and adding a comment
> in file_acquire_sample_rows() explaining why reject_limit is not enforced?
Attached is v2 documenting this in file-fdw.sgml and adding a comment in
file_acquire_sample_rows().
Regards,
Ayoub Kazar
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-file_fdw-Document-why-ANALYZE-does-not-enforce-REJECT_LIMIT.patch | text/x-patch | 2.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Burd | 2026-11-05 19:15:11 | Re: [RFC] Property-based testing for Postgres |
| Previous Message | Zakhar Pashkin | 2026-11-05 18:11:55 | Re: Print latency percentiles in pgbench |