| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Bryan Sayer <brysayer(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Additional options for COPY from |
| Date: | 2025-09-25 20:21:07 |
| Message-ID: | e410c26d-e8dd-4865-90ae-8769f989480c@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/25/25 11:49, Bryan Sayer wrote:
> Hi,
>
> I'm not sure if this is the best list to ask this (and I am very new to
> PostgreSQL) but I think more options are needed in the COPY from
> command, in order to better deal with exceptions. By exceptions I mean
> data not consistent with the format, empty rows, extra delimiters at the
> end of rows, etc.
What do you mean by '... deal with exceptions.'?
> *Bryan Sayer*
> Retired Demographer/Statistician
> /In a world in which you can be anything, *be kind*/
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashish Mukherjee | 2025-09-26 03:57:09 | Re: Enquiry about Percona TDE performance issues |
| Previous Message | David G. Johnston | 2025-09-25 20:18:27 | Re: Additional options for COPY from |