Jeremy Finzel <finzelj@xxxxxxxxx> writes: > On Mon, Apr 22, 2019 at 3:47 PM Tom Lane <tgl@xxxxxxxxxxxxx> wrote: >> Sure sounds to me like what you are setting is something client-side, >> not the server's log verbosity. It works for me: > I am running it differently - explicitly raising a LOG level message, not > an ERROR. The line of interest is the following: My question was about how you (think you are) setting log_error_verbosity, not what you're doing to produce the message. The decisions in elog.c about which fields to print in the server log do not depend on the latter. However... looking again at what elog.c does, I'm prompted to ask whether you're using plain or CSV log output. The CSV log format doesn't consider log_error_verbosity when deciding whether to output this field. regards, tom lane
