pgsql-server/ onfig/c-compiler.m4 /configure / ...

CVSROOT:    /cvsroot
Module name:    pgsql-server
Changes by:    tgl@postgresql.org    03/04/24 17:16:45

Modified files:
    config         : c-compiler.m4
    .              : configure configure.in
    doc/src/sgml   : protocol.sgml
    src/backend/catalog: namespace.c
    src/backend/commands: copy.c explain.c
    src/backend/executor: spi.c
    src/backend/lib: stringinfo.c
    src/backend/nodes: outfuncs.c
    src/backend/parser: parse_func.c parse_type.c scan.l
    src/backend/tcop: postgres.c
    src/backend/utils/adt: ruleutils.c varlena.c
    src/backend/utils/error: elog.c
    src/include/commands: copy.h
    src/include/lib: stringinfo.h
    src/include/libpq: pqcomm.h
    src/include    : pg_config.h.in
    src/include/utils: elog.h
    src/interfaces/libpq: fe-connect.c fe-exec.c libpq-int.h
    src/pl/plpgsql/src: pl_comp.c pl_exec.c plpgsql.h
    src/test/regress/expected: alter_table.out copy2.out domain.out
                               plpgsql.out
    src/test/regress/output: constraints.source

Log message:
    Infrastructure for upgraded error reporting mechanism.  elog.c is
    rewritten and the protocol is changed, but most elog calls are still
    elog calls.  Also, we need to contemplate mechanisms for controlling
    all this functionality --- eg, how much stuff should appear in the
    postmaster log?  And what API should libpq expose for it?