Fix the missing table sync due to improper invalidation handling.
We missed performing table sync if the invalidation happened while the
non-ready tables list was being prepared. This occurs because the sync
state was set to valid at the end of non-ready table list preparation
irrespective of the
Fix the missing table sync due to improper invalidation handling.
We missed performing table sync if the invalidation happened while the
non-ready tables list was being prepared. This occurs because the sync
state was set to valid at the end of non-ready table list preparation
irrespective of the
Fix the missing table sync due to improper invalidation handling.
We missed performing table sync if the invalidation happened while the
non-ready tables list was being prepared. This occurs because the sync
state was set to valid at the end of non-ready table list preparation
irrespective of the
Improve comment of DeallocateStmt->isall
This field is not used directly in the code, but it is important for
query jumbling to be able to make a difference between a named
DEALLOCATE and DEALLOCATE ALL (see bb45156f342c). This behavior is
tracked in the regression tests of pg_stat_statements, bu
Doc: fix minor oversight in ALTER DEFAULT PRIVILEGES ref page.
Since schemas have more than one kind of privilege, we should
use the synopsis form that shows the privilege being possibly
repeated.
Yugo Nagata
Discussion:
https://postgr.es/m/20240424155052.7ac0d0773e4ae27ab723f...@sraoss.co.jp
Doc: fix minor oversight in ALTER DEFAULT PRIVILEGES ref page.
Since schemas have more than one kind of privilege, we should
use the synopsis form that shows the privilege being possibly
repeated.
Yugo Nagata
Discussion:
https://postgr.es/m/20240424155052.7ac0d0773e4ae27ab723f...@sraoss.co.jp
Doc: fix minor oversight in ALTER DEFAULT PRIVILEGES ref page.
Since schemas have more than one kind of privilege, we should
use the synopsis form that shows the privilege being possibly
repeated.
Yugo Nagata
Discussion:
https://postgr.es/m/20240424155052.7ac0d0773e4ae27ab723f...@sraoss.co.jp
Doc: fix minor oversight in ALTER DEFAULT PRIVILEGES ref page.
Since schemas have more than one kind of privilege, we should
use the synopsis form that shows the privilege being possibly
repeated.
Yugo Nagata
Discussion:
https://postgr.es/m/20240424155052.7ac0d0773e4ae27ab723f...@sraoss.co.jp
Doc: fix minor oversight in ALTER DEFAULT PRIVILEGES ref page.
Since schemas have more than one kind of privilege, we should
use the synopsis form that shows the privilege being possibly
repeated.
Yugo Nagata
Discussion:
https://postgr.es/m/20240424155052.7ac0d0773e4ae27ab723f...@sraoss.co.jp
Doc: fix minor oversight in ALTER DEFAULT PRIVILEGES ref page.
Since schemas have more than one kind of privilege, we should
use the synopsis form that shows the privilege being possibly
repeated.
Yugo Nagata
Discussion:
https://postgr.es/m/20240424155052.7ac0d0773e4ae27ab723f...@sraoss.co.jp
On 08.04.24 03:25, Heikki Linnakangas wrote:
Refactor libpq state machine for negotiating encryption
This fixes the few corner cases noted in commit 705843d294, as shown
by the changes in the test.
Either this or something nearby appears to have broken the error
reporting from psql or libpq w
Add pg_logging_init() calls missing in commit ba3e6e2bca
As noticed by Michael Paquier.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/cc893b82370b5d68e0a72f5bb1663644a3a0351d
Modified Files
--
src/test/modules/test_json_parser/test_json_parser_increme
Doc: fix prompt in psql crosstabview example
The prompt in the crosstabview example was incorrectly indicating
an open parenthesis where there is none in the example query. Fix
by changing to the normal multi-line prompt.
Reported-by: y.sabu...@gmail.com
Discussion:
https://postgr.es/m/171369707
doc: Fix up spacing around verbatim DocBook elements
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/b53d58097d7d5712d819d06e0416dec0a7db2479
Modified Files
--
doc/src/sgml/func.sgml | 32
doc/src/sgml/ref
pg_combinebackup: Add --version to --help output
(It was already on the man page.)
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/83751691e9c89af15103220b62d78cf5be73dbfd
Modified Files
--
src/bin/pg_combinebackup/pg_combinebackup.c | 1 +
1 file change
doc: Correct jsonpath string literal escapes description
The paragraph describing the JavaScript string literals allowed in
jsonpath expressions unnecessarily mentions JSON by erroneously
listing \v as allowed by JSON and mentioning the \xNN and \u{N...}
backslash escapes as deviations from JSON w
doc: Correct jsonpath string literal escapes description
The paragraph describing the JavaScript string literals allowed in
jsonpath expressions unnecessarily mentions JSON by erroneously
listing \v as allowed by JSON and mentioning the \xNN and \u{N...}
backslash escapes as deviations from JSON w
doc: Correct jsonpath string literal escapes description
The paragraph describing the JavaScript string literals allowed in
jsonpath expressions unnecessarily mentions JSON by erroneously
listing \v as allowed by JSON and mentioning the \xNN and \u{N...}
backslash escapes as deviations from JSON w
doc: Correct jsonpath string literal escapes description
The paragraph describing the JavaScript string literals allowed in
jsonpath expressions unnecessarily mentions JSON by erroneously
listing \v as allowed by JSON and mentioning the \xNN and \u{N...}
backslash escapes as deviations from JSON w
doc: Correct jsonpath string literal escapes description
The paragraph describing the JavaScript string literals allowed in
jsonpath expressions unnecessarily mentions JSON by erroneously
listing \v as allowed by JSON and mentioning the \xNN and \u{N...}
backslash escapes as deviations from JSON w
doc: Correct jsonpath string literal escapes description
The paragraph describing the JavaScript string literals allowed in
jsonpath expressions unnecessarily mentions JSON by erroneously
listing \v as allowed by JSON and mentioning the \xNN and \u{N...}
backslash escapes as deviations from JSON w
pg_combinebackup: Put newer options in consistent order in --help and man page
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/3886530caa01cac7179fed6b6e1d303710c027d9
Modified Files
--
doc/src/sgml/ref/pg_combinebackup.sgml | 90 ++-
Doc: Use past tense for things which happened in the past
The paragraph on SSL compression is largely describing events which
took place many years ago, so reword with past tense.
Reviewed-by: Peter Eisentraut
Reviewed-by: Michael Paquier
Discussion:
https://postgr.es/m/eac70d46-e61c-4d71-a1e1
Support disallowing SSL renegotiation when using LibreSSL
LibreSSL doesn't support the SSL_OP_NO_RENEGOTIATION macro which is
used by OpenSSL, instead it has invented a similar one for client-
side renegotiation: SSL_OP_NO_CLIENT_RENEGOTIATION. This has been
supported since LibreSSL 2.5.1 which by
Support SSL_R_VERSION_TOO_LOW when using LibreSSL
The SSL_R_VERSION_TOO_LOW error reason is supported in LibreSSL since
LibreSSL 3.6.3, shipped in OpenBSD 7.2. SSL_R_VERSION_TOO_HIGH is on
the other hand not supported in any version of LibreSSL. Previously
we only checked for SSL_R_VERSION_TOO_H
pg_dump: Put new options in consistent order in --help and man page
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/256b4b060614f4e54e49bb43a54404af4f1ef61d
Modified Files
--
doc/src/sgml/ref/pg_dump.sgml | 42 +-
s
doc: Fix order of options on pg_createsubscriber man page
Some options were listed in an order that was inconsistent with the
--help output and everything else.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/286eea5d3ae33a8c22d46a051f8ac6069c8b779d
Modified Files
pg_walsummary: Document --version option
It was working, but it was not shown in the --help output or on the
man page.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/f994ed89a98b9aed405c760f157a10125eb8d567
Modified Files
--
doc/src/sgml/ref/pg_walsumm
28 matches
Mail list logo
