| From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Cannot COPY xmin? |
| Date: | 2024-02-27 18:20:06 |
| Message-ID: | CAFCRh-8LTZrtELwXsO04XT83sn2v_GpHWQ3=q11wLPi2yCL5ug@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi. I just tried adding the xmin pseudo-column to my COPY,
and I get an error. Using a regular SELECT works fine.
Is that normal? that's a `COPY tab(xmin, cols...) ...`
Do I need to switch to a `COPY (select xmin, cols... from tab) ...` to
access xmin?
And if I do that, any performance implications for the COPY?
The reason I'm using COPY is performance and its "streaming" behavior.
(modulo the "big row" non-streaming issue from my as-yet unanswered post
from today).
I'm thus interested in how a `COPY tab(cols...)` differs from a `COPY
(select cols from tab ...)` in terms of implementation and performance.
Thanks, --DD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2024-02-27 18:26:14 | Re: Cannot COPY xmin? |
| Previous Message | Adrian Klaver | 2024-02-27 18:09:36 | Re: Me again with an insert trigger problem |