On Sat, Apr 18, 2026 at 2:04 AM Maxym Kharchenko <[email protected]> wrote: > > Hello Fujii-san, > > There seems to be an inconsistency in the current patch. When a statement has > errors (for example, when it hits a table that does not exist), the full > statement is still being logged. > > Similar parameter: `log_parameter_max_length` has a companion > `log_parameter_max_length_on_error` to handle this case (commit: > 0b34e7d307e6, > https://github.com/postgres/postgres/commit/0b34e7d307e6a142ee94800e6d5f3e73449eeffd). > > Should the same treatment be added for `log_statement_max_length`?
I think extending log_statement_max_length, or adding something like log_statement_max_length_on_error, would be a good idea to cover statements logged on error. However, I think the current patch is good as it stands, so I'd recommend pursuing that as a separate patch after the current one is committed. Regards, -- Fujii Masao
