Translation updates
Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: c5b5ab1da828e1d7a012431e417f0b75b2450c8f
Branch
--
REL_16_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/b323fcc58cb15200572a8515bc9b5bb1882c4d42
Modified Files
--
On 06.09.23 09:12, Peter Eisentraut wrote:
Translation updates
Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: c5b5ab1da828e1d7a012431e417f0b75b2450c8f
Branch
--
REL_16_STABLE
Note, there were some large mechanical updates done across many
trans
Update comments to match location of definition
Commit cc50080a82 rearranged testsuites to reduce dependencies, but
missed to update a comment when moving an operator class definition.
Also fix a typo in that same comment while here.
Author: Suraj Kharage
Discussion:
https://postgr.es/m/CAF1DzP
doc: PG 16 relnotes: fix subscriber role permission description
Reported-by: Magnus Hagander
Discussion:
https://postgr.es/m/cabuevewbxi5oqqmj429lxjro1uu-fdkgskjtgjs5atomuje...@mail.gmail.com
Backpatch-through: 16 only
Branch
--
REL_16_STABLE
Details
---
https://git.postgresql.org/pg/
doc: mention that to_char() values are rounded
Reported-by: barsikda...@gmail.com
Diagnosed-by: Laurenz Albe
Discussion:
https://postgr.es/m/168991536429.626.9957835774751337...@wrigleys.postgresql.org
Author: Laurenz Albe
Backpatch-through: 11
Branch
--
REL_16_STABLE
Details
---
h
doc: mention that to_char() values are rounded
Reported-by: barsikda...@gmail.com
Diagnosed-by: Laurenz Albe
Discussion:
https://postgr.es/m/168991536429.626.9957835774751337...@wrigleys.postgresql.org
Author: Laurenz Albe
Backpatch-through: 11
Branch
--
REL_12_STABLE
Details
---
h
doc: mention that to_char() values are rounded
Reported-by: barsikda...@gmail.com
Diagnosed-by: Laurenz Albe
Discussion:
https://postgr.es/m/168991536429.626.9957835774751337...@wrigleys.postgresql.org
Author: Laurenz Albe
Backpatch-through: 11
Branch
--
REL_11_STABLE
Details
---
h
doc: mention that to_char() values are rounded
Reported-by: barsikda...@gmail.com
Diagnosed-by: Laurenz Albe
Discussion:
https://postgr.es/m/168991536429.626.9957835774751337...@wrigleys.postgresql.org
Author: Laurenz Albe
Backpatch-through: 11
Branch
--
master
Details
---
https://
doc: mention that to_char() values are rounded
Reported-by: barsikda...@gmail.com
Diagnosed-by: Laurenz Albe
Discussion:
https://postgr.es/m/168991536429.626.9957835774751337...@wrigleys.postgresql.org
Author: Laurenz Albe
Backpatch-through: 11
Branch
--
REL_13_STABLE
Details
---
h
doc: mention that to_char() values are rounded
Reported-by: barsikda...@gmail.com
Diagnosed-by: Laurenz Albe
Discussion:
https://postgr.es/m/168991536429.626.9957835774751337...@wrigleys.postgresql.org
Author: Laurenz Albe
Backpatch-through: 11
Branch
--
REL_15_STABLE
Details
---
h
doc: mention that to_char() values are rounded
Reported-by: barsikda...@gmail.com
Diagnosed-by: Laurenz Albe
Discussion:
https://postgr.es/m/168991536429.626.9957835774751337...@wrigleys.postgresql.org
Author: Laurenz Albe
Backpatch-through: 11
Branch
--
REL_14_STABLE
Details
---
h
Allow using syncfs() in frontend utilities.
This commit allows specifying a --sync-method in several frontend
utilities that must synchronize many files to disk (initdb,
pg_basebackup, pg_checksums, pg_dump, pg_rewind, and pg_upgrade).
On Linux, users can specify "syncfs" to synchronize the releva
Make enum for sync methods available to frontend code.
This commit renames RecoveryInitSyncMethod to DataDirSyncMethod and
moves it to common/file_utils.h. This is preparatory work for a
follow-up commit that will allow specifying the synchronization
method in frontend utilities such as pg_upgrad
Add support for syncfs() in frontend support functions.
This commit adds support for using syncfs() in fsync_pgdata() and
fsync_dir_recurse() (which have been renamed to sync_pgdata() and
sync_dir_recurse()). Like recovery_init_sync_method,
sync_pgdata() calls syncfs() for the data directory, eac
Disable 031_recovery_conflict.pl in 15 and 16.
This test fails due to known bugs in the test and the server. Those
will be fixed in master shortly and possibly back-patched a bit later,
but in the meantime it is unhelpful for package maintainers if the tests
randomly fail, and it's not a good tim
Disable 031_recovery_conflict.pl in 15 and 16.
This test fails due to known bugs in the test and the server. Those
will be fixed in master shortly and possibly back-patched a bit later,
but in the meantime it is unhelpful for package maintainers if the tests
randomly fail, and it's not a good tim
Fix recovery conflict SIGUSR1 handling.
We shouldn't be doing non-trivial work in signal handlers in general,
and in this case the handler could reach unsafe code and corrupt state.
It also clobbered its own "reason" code.
Move all recovery conflict decision logic into the next
CHECK_FOR_INTERRUP
Fix instability in 031_recovery_conflict.pl.
Where the test wants a VACUUM command to generate WAL that would
conflict with a session on the standby, it could transiently fail to do
so if it couldn't acquire a cleanup lock conditionally at that moment on
the primary. VACUUM FREEZE will wait, so u
pg_basebackup: Generate valid temporary slot names under PQbackendPID()
pgbouncer can cause PQbackendPID() to return negative values due to it
filling be_pid with random bytes (even these days pid_max can only be
set up to 2^22 on 64b machines on Linux, for example, so this cannot
happen with norm
pg_basebackup: Generate valid temporary slot names under PQbackendPID()
pgbouncer can cause PQbackendPID() to return negative values due to it
filling be_pid with random bytes (even these days pid_max can only be
set up to 2^22 on 64b machines on Linux, for example, so this cannot
happen with norm
pg_basebackup: Generate valid temporary slot names under PQbackendPID()
pgbouncer can cause PQbackendPID() to return negative values due to it
filling be_pid with random bytes (even these days pid_max can only be
set up to 2^22 on 64b machines on Linux, for example, so this cannot
happen with norm
pg_basebackup: Generate valid temporary slot names under PQbackendPID()
pgbouncer can cause PQbackendPID() to return negative values due to it
filling be_pid with random bytes (even these days pid_max can only be
set up to 2^22 on 64b machines on Linux, for example, so this cannot
happen with norm
pg_basebackup: Generate valid temporary slot names under PQbackendPID()
pgbouncer can cause PQbackendPID() to return negative values due to it
filling be_pid with random bytes (even these days pid_max can only be
set up to 2^22 on 64b machines on Linux, for example, so this cannot
happen with norm
pg_basebackup: Generate valid temporary slot names under PQbackendPID()
pgbouncer can cause PQbackendPID() to return negative values due to it
filling be_pid with random bytes (even these days pid_max can only be
set up to 2^22 on 64b machines on Linux, for example, so this cannot
happen with norm
pg_basebackup: Generate valid temporary slot names under PQbackendPID()
pgbouncer can cause PQbackendPID() to return negative values due to it
filling be_pid with random bytes (even these days pid_max can only be
set up to 2^22 on 64b machines on Linux, for example, so this cannot
happen with norm
25 matches
Mail list logo
