Update list of acknowledgments in release notes
current through 15113bfb467a84688744b57b74a14550878d0224
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/5483649cd6875c219beb10465b515ba096dc7f34
Modified Files
--
doc/src/sgml/release-15.sgml | 9 +
Translation updates
Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: 0a336c1e07ac371cf445a0cecac6b27720da228c
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/0570eba3dcf8c819a6b100b14e25290eaedb4b5a
Modified Files
--
Fix write/read of empty string fields in Nodes.
Historically, outToken has represented both NULL and empty-string
strings as "<>", which readfuncs.c then read as NULL, thus failing
to preserve empty-string fields accurately. Remarkably, this has
not caused any serious problems yet, but let's fix
Peter Eisentraut writes:
> Fix write/read of empty string fields in Nodes.
This really should've included a catversion bump, I think.
Maybe there are no cases where this affects a Node type
we can store today, but I'm unconvinced of that.
regards, tom lane
catversion bump
for 8999f5ed3cd7d26be1121d912086d04d134d398b
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/c07785d458c1ca69ad7cd3ebb8f4a1d953c3779b
Modified Files
--
src/include/catalog/catversion.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Don't lose precision for float fields of Nodes.
Historically we've been more worried about making the output of
float fields look pretty than whether they'd be read back exactly.
That won't work if we're to compare the read-back nodes for
equality, so switch to using the Ryu code for float output.
Enable WRITE_READ_PARSE_PLAN_TREES of rewritten utility statements
This was previously disabled because we lacked outfuncs/readfuncs
support for most utility statement types.
Reviewed-by: Tom Lane
Discussion:
https://www.postgresql.org/message-id/flat/4159834.1657405...@sss.pgh.pa.us
Branch
--
Implement WRITE_READ_PARSE_PLAN_TREES for raw parse trees
Reviewed-by: Tom Lane
Discussion:
https://www.postgresql.org/message-id/flat/4159834.1657405...@sss.pgh.pa.us
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/40ad8f9deed21f02b23eb034bfca87f7acc7562b
Author:
Doc: further adjust notes about pg_upgrade_output.d.
I'd misunderstood how it worked in 5f1048881.
Discussion: https://postgr.es/m/20220925215009.gc21...@telsasoft.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/fbd2bd15b0114bb900aa6986add2b359fec1b740
Modifie
Doc: further adjust notes about pg_upgrade_output.d.
I'd misunderstood how it worked in 5f1048881.
Discussion: https://postgr.es/m/20220925215009.gc21...@telsasoft.com
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/796aa20a11b4060e07b0864081e6977eb66b64bd
Doc: more tweaking of v15 release notes.
Per suggestions from Justin Pryzby.
Discussion: https://postgr.es/m/20220925215009.gc21...@telsasoft.com
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/780add2c32a7577f1eab81ae3d8802cd02c4f8fe
Modified Files
---
windows: remove date from version number in win32ver.rc
This may have served a purpose at some point, but these days it just
contributes to a non-reproducible build.
Reviewed-by: Peter Eisentraut
Discussion:
https://postgr.es/m/c5736f70-bb6d-8d25-e35c-e3d886e4e...@enterprisedb.com
Discussion:
Stamp 15rc1.
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/6abbd212b2828717fb3b10ed2925edf8f212e38d
Modified Files
--
configure| 18 +-
configure.ac | 2 +-
2 files changed, 10 insertions(+), 10 deletions(-)
Doc: last minute adjustment to the release notes
The change made in 9d9c02ccd also affects the dense_rank() function.
Mention this in the release notes.
Author: Jonathan S. Katz
Discussion:
https://postgr.es/m/5c6d3f50-e9b5-f62d-d58a-7b22eb91d...@postgresql.org
Branch
--
REL_15_STABLE
Deta
Remove dependency to StringInfo in xlogbackup.{c.h}
This was used as the returned result type of the generated contents for
the backup_label and backup history files. This is replaced by a simple
string, reducing the cleanup burden of all the callers of
build_backup_content().
Reviewed-by: Bhara
Mark ParallelMessagePending as sig_atomic_t
ParallelMessagePending was previously marked as a boolean which should
be fine on modern platforms, but the C standard recommends the use of
sig_atomic_t for variables manipulated in signal handlers.
Author: Hayato Kuroda
Discussion:
https://postgr.es/
meson: Include CFLAGS/c_args in summary and pg_config output
Previously arguments passed in via CFLAGS/-Dc_args were neither displayed in
meson's summary, nor in pg_config's output.
Reported-by: "wangw.f...@fujitsu.com"
Discussion:
https://postgr.es/m/os3pr01mb62751847bc9cd2db7b29ac129e...@os3p
meson: Set up absolute rpaths to libdir
While I (Andres) had planned to use relative rpaths, it looks like agreeing on
the precise path might take a bit. So set up absolute rpaths for now.
I'm pushing this fairly quickly after posting the patch as several hackers
fought with this issue.
Discussi
ci: Add hint about downloadable logs to README
I (Andres) chose to backpatch this to 15, as it seems better to keep the
README the same.
Author: James Coleman
Discussion:
https://postgr.es/m/caaaqye_7bxdjpk0ks_eqf1r6lzpc_rfb7kjhb_t3+ec4t6y...@mail.gmail.com
Backpatch: 15-, where CI came in
Bra
ci: Add hint about downloadable logs to README
I (Andres) chose to backpatch this to 15, as it seems better to keep the
README the same.
Author: James Coleman
Discussion:
https://postgr.es/m/caaaqye_7bxdjpk0ks_eqf1r6lzpc_rfb7kjhb_t3+ec4t6y...@mail.gmail.com
Backpatch: 15-, where CI came in
Bra
20 matches
Mail list logo
