doc PG relnotes: add attribution for time zone data files items
This is needed for a future script to add commit links; specifically we
need the closing parentheses of the attribution.
Backpatch-through: 12
Branch
--
REL_16_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/1
doc PG relnotes: add attribution for time zone data files items
This is needed for a future script to add commit links; specifically we
need the closing parentheses of the attribution.
Backpatch-through: 12
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/9
doc PG relnotes: add attribution for time zone data files items
This is needed for a future script to add commit links; specifically we
need the closing parentheses of the attribution.
Backpatch-through: 12
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/c
doc PG relnotes: add attribution for time zone data files items
This is needed for a future script to add commit links; specifically we
need the closing parentheses of the attribution.
Backpatch-through: 12
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/a
doc PG relnotes: add attribution for time zone data files items
This is needed for a future script to add commit links; specifically we
need the closing parentheses of the attribution.
Backpatch-through: 12
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/c
Run regression tests with timezone America/Los_Angeles.
Historically we've used timezone "PST8PDT", but the recent release
2024b of tzdb changes the definition of that zone in a way that
breaks many test cases concerned with dates before 1970. Although
we've not yet adopted 2024b into our own tre
Run regression tests with timezone America/Los_Angeles.
Historically we've used timezone "PST8PDT", but the recent release
2024b of tzdb changes the definition of that zone in a way that
breaks many test cases concerned with dates before 1970. Although
we've not yet adopted 2024b into our own tre
Run regression tests with timezone America/Los_Angeles.
Historically we've used timezone "PST8PDT", but the recent release
2024b of tzdb changes the definition of that zone in a way that
breaks many test cases concerned with dates before 1970. Although
we've not yet adopted 2024b into our own tre
Run regression tests with timezone America/Los_Angeles.
Historically we've used timezone "PST8PDT", but the recent release
2024b of tzdb changes the definition of that zone in a way that
breaks many test cases concerned with dates before 1970. Although
we've not yet adopted 2024b into our own tre
Run regression tests with timezone America/Los_Angeles.
Historically we've used timezone "PST8PDT", but the recent release
2024b of tzdb changes the definition of that zone in a way that
breaks many test cases concerned with dates before 1970. Although
we've not yet adopted 2024b into our own tre
Run regression tests with timezone America/Los_Angeles.
Historically we've used timezone "PST8PDT", but the recent release
2024b of tzdb changes the definition of that zone in a way that
breaks many test cases concerned with dates before 1970. Although
we've not yet adopted 2024b into our own tre
Run regression tests with timezone America/Los_Angeles.
Historically we've used timezone "PST8PDT", but the recent release
2024b of tzdb changes the definition of that zone in a way that
breaks many test cases concerned with dates before 1970. Although
we've not yet adopted 2024b into our own tre
Add commit 7229ebe011df to .git-blame-ignore-revs.
Branch
--
REL_17_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/fca91b5c903a0d810492eed5a207032f7ee6e175
Modified Files
--
.git-blame-ignore-revs | 3 +++
1 file changed, 3 insertions(+)
Add commit 7229ebe011df to .git-blame-ignore-revs.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/f64074c88c067b4733ae439afae46ad61e45474b
Modified Files
--
.git-blame-ignore-revs | 3 +++
1 file changed, 3 insertions(+)
doc PG 17 relnotes: adjust SGML format for commit add script
Backpatch-through: 17 only
Branch
--
REL_17_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/77120dd08113dcb94c01f581408b50240bd24641
Modified Files
--
doc/src/sgml/release-17.sgml | 5 ++---
1 file chan
doc PG 17 relnotes: remove commit link whose comment was removed
Backpatch-through: 17 only
Branch
--
REL_17_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/4a898075690781a95159244719d4dcef6fd153da
Modified Files
--
doc/src/sgml/release-17.sgml | 1 -
1 file chang
Remove obsolete comment in pg_stat_statements.
Commit 76db9cb63 removed the use of multiple nesting counters,
but missed one comment describing that arrangement.
Back-patch to v17 where 76db9cb63 came in, just to avoid confusion.
Julien Rouhaud
Discussion:
https://postgr.es/m/gfcwh3zjxc2vyglta
Remove obsolete comment in pg_stat_statements.
Commit 76db9cb63 removed the use of multiple nesting counters,
but missed one comment describing that arrangement.
Back-patch to v17 where 76db9cb63 came in, just to avoid confusion.
Julien Rouhaud
Discussion:
https://postgr.es/m/gfcwh3zjxc2vyglta
doc PG 17 relnotes: update to current
Backpatch-through: 17 only
Branch
--
REL_17_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/54497e0ed8670f52ceb8dfc5949023a61daeec59
Modified Files
--
doc/src/sgml/release-17.sgml | 5 -
1 file changed, 4 insertions(+), 1
Improve meson's detection of perl build flags
The current method of detecting perl build flags breaks if the path to
perl contains a space. This change makes two improvements. First,
instead of getting a list of ldflags and ccdlflags and then trying to
filter those out of the reported ldopts, we t
Improve meson's detection of perl build flags
The current method of detecting perl build flags breaks if the path to
perl contains a space. This change makes two improvements. First,
instead of getting a list of ldflags and ccdlflags and then trying to
filter those out of the reported ldopts, we t
Improve meson's detection of perl build flags
The current method of detecting perl build flags breaks if the path to
perl contains a space. This change makes two improvements. First,
instead of getting a list of ldflags and ccdlflags and then trying to
filter those out of the reported ldopts, we t
doc PG 17 relnotes: move EXPLAIN items to their own section
Reported-by: Álvaro Herrera
Discussion: https://postgr.es/m/202409111750.xtcbl7ppdoyn@alvherre.pgsql
Backpatch-through: 17 only
Branch
--
REL_17_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/984702d0ee9b196dd0a6
Only define NO_THREAD_SAFE_LOCALE for MSVC plperl when required
Latest versions of Strawberry Perl define USE_THREAD_SAFE_LOCALE, and we
therefore get a handshake error when building against such instances.
The solution is to perform a test to see if USE_THREAD_SAFE_LOCALE is
defined and only defi
Only define NO_THREAD_SAFE_LOCALE for MSVC plperl when required
Latest versions of Strawberry Perl define USE_THREAD_SAFE_LOCALE, and we
therefore get a handshake error when building against such instances.
The solution is to perform a test to see if USE_THREAD_SAFE_LOCALE is
defined and only defi
Only define NO_THREAD_SAFE_LOCALE for MSVC plperl when required
Latest versions of Strawberry Perl define USE_THREAD_SAFE_LOCALE, and we
therefore get a handshake error when building against such instances.
The solution is to perform a test to see if USE_THREAD_SAFE_LOCALE is
defined and only defi
Only define NO_THREAD_SAFE_LOCALE for MSVC plperl when required
Latest versions of Strawberry Perl define USE_THREAD_SAFE_LOCALE, and we
therefore get a handshake error when building against such instances.
The solution is to perform a test to see if USE_THREAD_SAFE_LOCALE is
defined and only defi
Only define NO_THREAD_SAFE_LOCALE for MSVC plperl when required
Latest versions of Strawberry Perl define USE_THREAD_SAFE_LOCALE, and we
therefore get a handshake error when building against such instances.
The solution is to perform a test to see if USE_THREAD_SAFE_LOCALE is
defined and only defi
Only define NO_THREAD_SAFE_LOCALE for MSVC plperl when required
Latest versions of Strawberry Perl define USE_THREAD_SAFE_LOCALE, and we
therefore get a handshake error when building against such instances.
The solution is to perform a test to see if USE_THREAD_SAFE_LOCALE is
defined and only defi
Only define NO_THREAD_SAFE_LOCALE for MSVC plperl when required
Latest versions of Strawberry Perl define USE_THREAD_SAFE_LOCALE, and we
therefore get a handshake error when building against such instances.
The solution is to perform a test to see if USE_THREAD_SAFE_LOCALE is
defined and only defi
30 matches
Mail list logo
