On Mon, Sep 14, 2020 at 06:19:38AM +, Noah Misch wrote:
> Fix race in test of pg_switch_wal().
>
> The test failed when something added WAL between pg_switch_wal() and
> pg_current_wal_lsn(), seen on buildfarm members hornet and sungazer.
> Fix v10, v9.6 and v9.5 by making this code mirror its
Translation updates
Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: 00c0d74fc1f1f2a831077fdf3655c6ae5eeceac3
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/bab6f77f24407e0924dac292af9e65016fce99bf
Modified Files
--
On 9/10/20 1:14 PM, Tom Lane wrote:
> Doc: fill in "major enhancements" list in v13 release notes.
>
> Jonathan S. Katz, minor tweaks by me
>
> Discussion:
> https://postgr.es/m/[email protected]
>
> Branch
> --
> REL_13_STABLE
>
> Details
> ---
> https:
On Mon, Sep 14, 2020 at 3:28 PM Andrew Dunstan <
[email protected]> wrote:
>
> On 9/10/20 1:14 PM, Tom Lane wrote:
> > Doc: fill in "major enhancements" list in v13 release notes.
> >
> > Jonathan S. Katz, minor tweaks by me
> >
> > Discussion:
> https://postgr.es/m/448a382b-ae07-3126
Make walsenders show their replication commands in pg_stat_activity.
A walsender process that has executed a SQL command left the text of
that command in pg_stat_activity.query indefinitely, which is quite
confusing if it's in RUNNING state but not doing that query. An easy
and useful fix is to t
Stamp 13rc1.
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/efea2b85fa2c3dec1c8039f1c97fcfe53ee5e82c
Modified Files
--
configure| 18 +-
configure.in | 2 +-
2 files changed, 10 insertions(+), 10 deletions(-)
On Thu, 10 Sep 2020 at 06:41, Peter Eisentraut wrote:
> src/backend/utils/adt/dbsize.c| 21 ++
This change introduced a new compiler warning on MSVC.
src\backend\utils\adt\dbsize.c(630): warning C4334: '<<': result of
32-bit shift implicitly converted to 64 bits (was 64-bit shift
int
Fix compiler warning
Introduced in 0aa8f7640.
MSVC warned about performing 32-bit bit shifting when it appeared like we
might like a 64-bit result. We did, but it just so happened that none of
the calls to this function could have caused the 32-bit shift to overflow.
Here we just cast the const
