From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, jian(dot)universality(at)gmail(dot)com, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
Subject: | Re: Add new error_action COPY ON_ERROR "log" |
Date: | 2024-03-07 07:18:12 |
Message-ID: | CALj2ACXLf8m5R_UiXPG2gDh8JmNV-hidXQkyrNnLE2=1OCrE2g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Mar 7, 2024 at 9:30 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> Is a boolean the best interface for the end-user, though? Maybe
> something like a "mode" value would speak more than a yes/no from the
> start, say a "default" mode to emit only the last LOG and a "verbose"
> for the whole set in the case of ON_ERROR? That could use an enum
> from the start internally, but that's an implementation detail.
I'm okay with it. But, help me understand it better. We want the
'log_verbosity' clause to have options 'default' and 'verbose', right?
And, later it can also be extended to contain all the LOG levels like
'notice', 'error', 'info' , 'debugX' etc. depending on the need,
right?
One more thing, how does it sound using both verbosity and verbose in
log_verbosity verbose something like below? Is this okay?
COPY check_ign_err FROM STDIN WITH (on_error ignore, log_verbosity verbose);
--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bharath Rupireddy | 2024-03-07 07:20:33 | Re: Add new error_action COPY ON_ERROR "log" |
Previous Message | Richard Guo | 2024-03-07 07:14:09 | Re: Get rid of the excess semicolon in planner.c |