Re: [patch] pg_basebackup: mention that spread checkpoints are the default in --help - Mailing list pgsql-hackers
From | Shlok Kyal |
---|---|
Subject | Re: [patch] pg_basebackup: mention that spread checkpoints are the default in --help |
Date | |
Msg-id | CANhcyEUjTgy0bm4187VRSx+zEHHgyQ7x9cmFvArgPLoyZ5uC3A@mail.gmail.com Whole thread Raw |
In response to | Re: [patch] pg_basebackup: mention that spread checkpoints are the default in --help (Michael Banck <mbanck@gmx.net>) |
Responses |
Re: [patch] pg_basebackup: mention that spread checkpoints are the default in --help
|
List | pgsql-hackers |
Hi, On Thu, 26 Oct 2023 at 13:58, Michael Banck <mbanck@gmx.net> wrote: > > Hi, > > On Wed, Oct 25, 2023 at 04:36:41PM +0200, Peter Eisentraut wrote: > > On 19.10.23 11:39, Michael Banck wrote: > > > Hi, > > > > > > I believed that spread (not fast) checkpoints are the default in > > > pg_basebackup, but noticed that --help does not specify which is which - > > > contrary to the reference documentation. > > > > > > So I propose the small attached patch to clarify that. > > > > > printf(_(" -c, --checkpoint=fast|spread\n" > > >- " set fast or spread checkpointing\n")); > > >+ " set fast or spread (default) > > checkpointing\n")); > > > > Could we do like > > > > -c, --checkpoint=fast|spread > > set fast or spread checkpointing > > (default: spread) > > > > This seems to be easier to read. > > Yeah, we could do that. But then again the question pops up what to do > about the other option that mentions defaults (-F) and the others which > have a default but it is not spelt out yet (-X, -Z at least) (output is > still from v15, additional options have been added since): > > -F, --format=p|t output format (plain (default), tar) > -X, --wal-method=none|fetch|stream > include required WAL files with specified method > -Z, --compress=0-9 compress tar output with given compression level > > So, my personal opinion is that we should really document -c because it > is quite user-noticable compared to the others. > > So attached is a new version with just your proposed change for now. > > > Michael I went through the Cfbot for this patch and found out that the build is failing with the following error (Link: https://cirrus-ci.com/task/4648506929971200?logs=build#L1217): [08:34:47.625] FAILED: src/bin/pg_basebackup/pg_basebackup.p/pg_basebackup.c.o [08:34:47.625] ccache cc -Isrc/bin/pg_basebackup/pg_basebackup.p -Isrc/include -I../src/include -Isrc/interfaces/libpq -I../src/interfaces/libpq -Isrc/include/catalog -Isrc/include/nodes -Isrc/include/utils -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -fno-strict-aliasing -fwrapv -fexcess-precision=standard -D_GNU_SOURCE -Wmissing-prototypes -Wpointer-arith -Werror=vla -Wendif-labels -Wmissing-format-attribute -Wimplicit-fallthrough=3 -Wcast-function-type -Wshadow=compatible-local -Wformat-security -Wdeclaration-after-statement -Wno-format-truncation -Wno-stringop-truncation -pthread -MD -MQ src/bin/pg_basebackup/pg_basebackup.p/pg_basebackup.c.o -MF src/bin/pg_basebackup/pg_basebackup.p/pg_basebackup.c.o.d -o src/bin/pg_basebackup/pg_basebackup.p/pg_basebackup.c.o -c ../src/bin/pg_basebackup/pg_basebackup.c [08:34:47.625] ../src/bin/pg_basebackup/pg_basebackup.c: In function ‘usage’: [08:34:47.625] ../src/bin/pg_basebackup/pg_basebackup.c:411:5: warning: statement with no effect [-Wunused-value] [08:34:47.625] 411 | " (default: spread)\n")); [08:34:47.625] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [08:34:47.625] ../src/bin/pg_basebackup/pg_basebackup.c:411:51: error: expected ‘;’ before ‘)’ token [08:34:47.625] 411 | " (default: spread)\n")); [08:34:47.625] | ^ [08:34:47.625] | ; [08:34:47.625] ../src/bin/pg_basebackup/pg_basebackup.c:411:51: error: expected statement before ‘)’ token [08:34:47.625] ../src/bin/pg_basebackup/pg_basebackup.c:411:52: error: expected statement before ‘)’ token [08:34:47.625] 411 | " (default: spread)\n")); [08:34:47.625] | ^ [08:34:47.629] [1210/1832] Compiling C object src/bin/pg_dump/libpgdump_common.a.p/parallel.c.o [08:34:47.639] [1211/1832] Compiling C object src/bin/pg_basebackup/pg_recvlogical.p/pg_recvlogical.c.o [08:34:47.641] [1212/1832] Linking static target src/bin/pg_basebackup/libpg_basebackup_common.a [08:34:47.658] [1213/1832] Compiling C object src/bin/pg_dump/libpgdump_common.a.p/compress_io.c.o [08:34:47.669] [1214/1832] Compiling C object src/bin/pg_dump/libpgdump_common.a.p/compress_lz4.c.o [08:34:47.678] [1215/1832] Compiling C object src/bin/pg_dump/libpgdump_common.a.p/compress_zstd.c.o [08:34:47.692] [1216/1832] Compiling C object src/bin/pg_dump/libpgdump_common.a.p/dumputils.c.o [08:34:47.692] ninja: build stopped: subcommand failed. I also see that patch is marked 'Ready for Committer' on commitfest. Just wanted to make sure, you are aware of this error. Thanks, Shlok Kumar Kyal
pgsql-hackers by date: