Rename functions to avoid future conflicts
Rename range_serialize/range_deserialize to
brin_range_serialize/brin_range_deserialize, since there are already
public range_serialize/range_deserialize in rangetypes.h.
Author: Paul A. Jungwirth
Discussion:
https://www.postgresql.org/message-id/ca+re
Make EXEC_BACKEND more convenient on Linux and FreeBSD.
Try to disable ASLR when building in EXEC_BACKEND mode, to avoid random
memory mapping failures while testing. For developer use only, no
effect on regular builds.
Suggested-by: Andres Freund
Tested-by: Bossart, Nathan
Discussion:
https:
Avoid warning about uninitialized value in MSVC python3 tests
Juan José Santamaría Flecha
Backpatch to all live branches
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/1cd46f168fda4d819e315eacf3d4f3d5aa84859c
Modified Files
--
src/tools/msvc/vc
Avoid warning about uninitialized value in MSVC python3 tests
Juan José Santamaría Flecha
Backpatch to all live branches
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/32cd4264ccfc00234c6500913800983ca1073729
Modified Files
--
src/tools/msvc/vc
Avoid warning about uninitialized value in MSVC python3 tests
Juan José Santamaría Flecha
Backpatch to all live branches
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/03c545b66f748b9318d13bbc90f05f136a465484
Modified Files
--
src/tools/msvc/vc
Avoid warning about uninitialized value in MSVC python3 tests
Juan José Santamaría Flecha
Backpatch to all live branches
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/90657b42bfd592d906989023886ff2875ff2ae95
Modified Files
--
src/tools/msvc/vcregress
Avoid warning about uninitialized value in MSVC python3 tests
Juan José Santamaría Flecha
Backpatch to all live branches
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/ab3764a417ff58f28b62831ca2cabbb6cfd2133a
Modified Files
--
src/tools/msvc/vc
Avoid warning about uninitialized value in MSVC python3 tests
Juan José Santamaría Flecha
Backpatch to all live branches
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/5b2cb9c29e09419bcce2e1be47a78a7e3d0a1156
Modified Files
--
src/tools/msvc/vc
Doc: fix bogus example about ambiguous timestamps.
I had a brain fade in commit d32899157, and used 2:30AM as the
example timestamp for both spring-forward and fall-back cases.
But it's not actually ambiguous at all in the fall-back case,
because that transition is from 2AM to 1AM under USA rules.
Doc: fix bogus example about ambiguous timestamps.
I had a brain fade in commit d32899157, and used 2:30AM as the
example timestamp for both spring-forward and fall-back cases.
But it's not actually ambiguous at all in the fall-back case,
because that transition is from 2AM to 1AM under USA rules.
Doc: fix bogus example about ambiguous timestamps.
I had a brain fade in commit d32899157, and used 2:30AM as the
example timestamp for both spring-forward and fall-back cases.
But it's not actually ambiguous at all in the fall-back case,
because that transition is from 2AM to 1AM under USA rules.
Doc: fix bogus example about ambiguous timestamps.
I had a brain fade in commit d32899157, and used 2:30AM as the
example timestamp for both spring-forward and fall-back cases.
But it's not actually ambiguous at all in the fall-back case,
because that transition is from 2AM to 1AM under USA rules.
Doc: fix bogus example about ambiguous timestamps.
I had a brain fade in commit d32899157, and used 2:30AM as the
example timestamp for both spring-forward and fall-back cases.
But it's not actually ambiguous at all in the fall-back case,
because that transition is from 2AM to 1AM under USA rules.
Doc: fix bogus example about ambiguous timestamps.
I had a brain fade in commit d32899157, and used 2:30AM as the
example timestamp for both spring-forward and fall-back cases.
But it's not actually ambiguous at all in the fall-back case,
because that transition is from 2AM to 1AM under USA rules.
Improve error handling of cryptohash computations
The existing cryptohash facility was causing problems in some code paths
related to MD5 (frontend and backend) that relied on the fact that the
only type of error that could happen would be an OOM, as the MD5
implementation used in PostgreSQL ~13 (
Improve error handling of cryptohash computations
The existing cryptohash facility was causing problems in some code paths
related to MD5 (frontend and backend) that relied on the fact that the
only type of error that could happen would be an OOM, as the MD5
implementation used in PostgreSQL ~13 (
On Thu, Jan 6, 2022 at 7:46 AM Tom Lane wrote:
> Alvaro Herrera writes:
> > This also changes what tgisinternal means in some cases. Currently,
> > it means either that the trigger is an internal implementation object
> > of a foreign key constraint, or a "child" trigger on a partition
> > clone
Fix typo in rewriteheap.c.
Author: Bharath Rupireddy
Discussion:
https://postgr.es/m/calj2acw7svffw8r2ukh6oqm1knpt8aqmg61ksbpk0s2phhf...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/dbfa1022e4b63e71c4313f4d61a20ff97f2fb134
Modified Files
Update docs of logical replication for commit 8d74fc96db.
After commit 8d74fc96db, the details of logical replication conflicts can
be found in pg_stat_subscription_workers view.
Author: Masahiko Sawada
Reviewed-by: Amit Kapila
Discussion:
https://postgr.es/m/cad21aoc+zm5tgn8x88ajzycx0g_eieuu5xd
19 matches
Mail list logo
