| From: | Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Document COPY FROM WHERE restrictions on generated and system columns |
| Date: | 2026-07-02 13:16:41 |
| Message-ID: | CAJTYsWXij=ZzKDqVMTyGR7=Suf5CJfezBYHyf7+2GWk_CPpUVw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Hi,
On Thu, 2 Jul 2026 at 18:41, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> Hi,
>
> I found that generated columns and system columns cannot be used in
> COPY FROM WHERE expressions, but the COPY docs still mentions
> only the restriction on subqueries.
>
> So I've created the attached patch which updates the docs to also list
> generated columns and system columns as unsupported in COPY FROM WHERE
> expressions.
>
> Since generated columns have been rejected in COPY FROM WHERE since
> v13, that docs change should be backpatched to all supported branches.
> But the system-column restriction was introduced in v19, so that part
> does not need to be backpatched.
>
> Thoughts?
>
Thanks for the patch!
I think it makes sense to add the system columns and generated
columns limitation to the documentation, patch LGTM.
Regards,
Ayush
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-07-03 10:19:28 | Re: doc: Clarify ANALYZE VERBOSE output |
| Previous Message | David G. Johnston | 2026-06-30 16:51:30 | Re: glossary Data page |