2011-01-23 12:21:23 +01:00
|
|
|
# src/bin/pg_basebackup/nls.mk
|
2011-06-26 19:08:38 +02:00
|
|
|
CATALOG_NAME = pg_basebackup
|
2022-07-13 20:29:10 +02:00
|
|
|
GETTEXT_FILES = $(FRONTEND_COMMON_GETTEXT_FILES) \
|
|
|
|
|
bbstreamer_file.c \
|
|
|
|
|
bbstreamer_gzip.c \
|
|
|
|
|
bbstreamer_inject.c \
|
|
|
|
|
bbstreamer_lz4.c \
|
|
|
|
|
bbstreamer_tar.c \
|
|
|
|
|
bbstreamer_zstd.c \
|
|
|
|
|
pg_basebackup.c \
|
2024-03-25 12:30:55 +01:00
|
|
|
pg_createsubscriber.c \
|
2022-07-13 20:29:10 +02:00
|
|
|
pg_receivewal.c \
|
|
|
|
|
pg_recvlogical.c \
|
|
|
|
|
receivelog.c \
|
|
|
|
|
streamutil.c \
|
|
|
|
|
walmethods.c \
|
Rename backup_compression.{c,h} to compression.{c,h}
Compression option handling (level, algorithm or even workers) can be
used across several parts of the system and not only base backups.
Structures, objects and routines are renamed in consequence, to remove
the concept of base backups from this part of the code making this
change straight-forward.
pg_receivewal, that has gained support for LZ4 since babbbb5, will make
use of this infrastructure for its set of compression options, bringing
more consistency with pg_basebackup. This cleanup needs to be done
before releasing a beta of 15. pg_dump is a potential future target, as
well, and adding more compression options to it may happen in 16~.
Author: Michael Paquier
Reviewed-by: Robert Haas, Georgios Kokolatos
Discussion: https://postgr.es/m/YlPQGNAAa04raObK@paquier.xyz
2022-04-12 06:38:54 +02:00
|
|
|
../../common/compression.c \
|
2022-04-09 15:46:37 +02:00
|
|
|
../../common/fe_memutils.c \
|
|
|
|
|
../../common/file_utils.c \
|
2022-05-09 07:17:08 +02:00
|
|
|
../../fe_utils/option_utils.c \
|
2022-04-09 15:46:37 +02:00
|
|
|
../../fe_utils/recovery_gen.c
|
2023-05-08 06:15:26 +02:00
|
|
|
GETTEXT_TRIGGERS = $(FRONTEND_COMMON_GETTEXT_TRIGGERS) simple_prompt
|
Unified logging system for command-line programs
This unifies the various ad hoc logging (message printing, error
printing) systems used throughout the command-line programs.
Features:
- Program name is automatically prefixed.
- Message string does not end with newline. This removes a common
source of inconsistencies and omissions.
- Additionally, a final newline is automatically stripped, simplifying
use of PQerrorMessage() etc., another common source of mistakes.
- I converted error message strings to use %m where possible.
- As a result of the above several points, more translatable message
strings can be shared between different components and between
frontends and backend, without gratuitous punctuation or whitespace
differences.
- There is support for setting a "log level". This is not meant to be
user-facing, but can be used internally to implement debug or
verbose modes.
- Lazy argument evaluation, so no significant overhead if logging at
some level is disabled.
- Some color in the messages, similar to gcc and clang. Set
PG_COLOR=auto to try it out. Some colors are predefined, but can be
customized by setting PG_COLORS.
- Common files (common/, fe_utils/, etc.) can handle logging much more
simply by just using one API without worrying too much about the
context of the calling program, requiring callbacks, or having to
pass "progname" around everywhere.
- Some programs called setvbuf() to make sure that stderr is
unbuffered, even on Windows. But not all programs did that. This
is now done centrally.
Soft goals:
- Reduces vertical space use and visual complexity of error reporting
in the source code.
- Encourages more deliberate classification of messages. For example,
in some cases it wasn't clear without analyzing the surrounding code
whether a message was meant as an error or just an info.
- Concepts and terms are vaguely aligned with popular logging
frameworks such as log4j and Python logging.
This is all just about printing stuff out. Nothing affects program
flow (e.g., fatal exits). The uses are just too varied to do that.
Some existing code had wrappers that do some kind of print-and-exit,
and I adapted those.
I tried to keep the output mostly the same, but there is a lot of
historical baggage to unwind and special cases to consider, and I
might not always have succeeded. One significant change is that
pg_rewind used to write all error messages to stdout. That is now
changed to stderr.
Reviewed-by: Donald Dong <xdong@csumb.edu>
Reviewed-by: Arthur Zakirov <a.zakirov@postgrespro.ru>
Discussion: https://www.postgresql.org/message-id/flat/6a609b43-4f57-7348-6480-bd022f924310@2ndquadrant.com
2019-04-01 14:24:37 +02:00
|
|
|
GETTEXT_FLAGS = $(FRONTEND_COMMON_GETTEXT_FLAGS)
|
