| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Sbob <sbob(at)quadratum-braccas(dot)com> |
| Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ERROR Inserting into partition |
| Date: | 2024-10-22 14:47:32 |
| Message-ID: | CAKFQuwbOfs-vtxODz9o8_mHWOu2=kfYjL17NUTO7pp6C+Wo1kQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
>
>
> INSERT INTO part_schema.cust_info_5
> ( cust_last_name)
> SELECT l_name from public.global_addr WHERE l_name = 'NELL';
> ERROR: new row for relation "cust_info_5" violates partition constraint
> DETAIL: Failing row containd (null, null, null, null, null, 'NELL',
> null, null, null, null, null,null).
>
>
Your to: address for this email is so confusing...and this really isn't
either a performance issue (meaning speed, not failure to perform at all)
or admin issue (general advice for running the server). It seems like a
bug report, though one missing the most critical piece of information, the
version.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-10-22 14:53:34 | Re: ERROR Inserting into partition |
| Previous Message | Sbob | 2024-10-22 14:36:26 | ERROR Inserting into partition |