| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: COPY TO regression with psql -c |
| Date: | 2026-08-12 19:53:17 |
| Message-ID: | CAN4CZFOY3Z3zH4r0hfWt6Tvvkc4GGz6VR2b_6uCdLfb3U4AJ9A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> I took a brief look at this. The question the code immediately raises
> is "what to do if we get PSCAN_BACKSLASH?" ...
Yeah, I forgot to mention this in the email / commit but I checked
this and decided that it's a non-issue because we don't support it. I
added a comment about it, if support for that gets implemented in the
future, we can also extend this logic.
I dropped the reset buffer call and moved the test to the btasic est -
there's no reason to keep it separate. I just keep forgetting that I
should extend existing tests instead of adding new. Attached v2.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-psql-count-every-COPY-FROM-STDIN-when-scanning-a-.patch | application/octet-stream | 4.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Parragi | 2026-08-12 20:38:04 | Re: MERGE/SPLIT PARTITIONS issues/questions |
| Previous Message | Nathan Bossart | 2026-08-12 19:50:34 | Re: Should CUSTER (ANALYZE) work? |