Re: Add new error_action COPY ON_ERROR "log"
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
To: torikoshia <torikoshia@oss.nttdata.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>,
jian.universality@gmail.com, Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2024-02-17T06:00:00Z
Lists: pgsql-hackers
Attachments
- v2-0001-Add-detailed-info-when-COPY-skips-soft-errors.patch (application/x-patch) patch v2-0001
On Fri, Feb 16, 2024 at 8:17 PM torikoshia <torikoshia@oss.nttdata.com> wrote: > > I may be wrong since I seldom do data loading tasks, but I greed with > you. > > I also a little concerned about the case where there are many malformed > data and it causes lots of messages, but the information is usually > valuable and if users don't need it, they can suppress it by changing > client_min_messages. > > Currently both summary of failures and individual information is logged > in NOTICE level. > If we should assume that there are cases where only summary information > is required, it'd be useful to set lower log level, i.e. LOG to the > individual information. How about we emit the summary at INFO level and individual information at NOTICE level? With this, the summary is given a different priority than the individual info. With SET client_min_messages = WARNING; one can still get the summary but not the individual info. Also, to get all of these into server log, one can SET log_min_messages = INFO; or SET log_min_messages = NOTICE;. Thoughts? -- Bharath Rupireddy PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
Commits
-
Add new COPY option LOG_VERBOSITY.
- f5a227895e17 17.0 landed
-
Add tests for more row patterns with COPY FROM .. (ON_ERROR ignore)
- a189ed49d629 17.0 landed
-
Support writing "CREATE/ALTER TABLE ... SET STORAGE DEFAULT".
- b9424d014e19 16.0 cited