On 2022/02/18 19:59, Peter Eisentraut wrote:
On 18.02.22 09:24, Fujii Masao wrote:
Or even backtrace should be logged by write_stderr() so that it's written to
eventlog if necessary? I just wonder why backtrace_symbols_fd() is used only in
ExceptionalCondition().
Probably because it was si
On Thursday, February 17, 2022, PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/sql-copy.html
> Description:
>
> The documentation states that headers are only used for CSV files, but
> there
> is a hea
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/14/sql-copy.html
Description:
The documentation states that headers are only used for CSV files, but there
is a header "PGCOPY" when using a BINARY export. e.g.
COPY (SELECT zipfile FROM file
On 18.02.22 09:24, Fujii Masao wrote:
Or even backtrace should be logged by write_stderr() so that it's
written to eventlog if necessary? I just wonder why
backtrace_symbols_fd() is used only in ExceptionalCondition().
Probably because it was simpler. It would also make sense to convert
the
On 2022/02/18 16:07, Peter Eisentraut wrote:
On 07.02.22 17:42, Fujii Masao wrote:
On 2022/02/08 1:12, Peter Eisentraut wrote:
This change looks good to me. There is also backtrace code in assert.c that
might want the same treatment.
Yeah, that's good idea! The attached patch also adds t
