Re: Add new error_action COPY ON_ERROR "log"
От | Bharath Rupireddy |
---|---|
Тема | Re: Add new error_action COPY ON_ERROR "log" |
Дата | |
Msg-id | CALj2ACXLf8m5R_UiXPG2gDh8JmNV-hidXQkyrNnLE2=1OCrE2g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Add new error_action COPY ON_ERROR "log" (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: Add new error_action COPY ON_ERROR "log"
|
Список | pgsql-hackers |
On Thu, Mar 7, 2024 at 9:30 AM Michael Paquier <michael@paquier.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
В списке pgsql-hackers по дате отправления: