Doc fixes for commit 1e16af8ab5.
Discussion:
https://postgr.es/m/275c47ea-e7f3-e654-c99a-63bc11699...@enterprisedb.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/f4a9422c0c37ba638adbab853b8badb98a53ce04
Modified Files
--
doc/src/sgml/charset.sgml
nbtree VACUUM: cope with right sibling link corruption.
Avoid "right sibling's left-link doesn't match" errors when vacuuming a
corrupt nbtree index. Just LOG the issue and press on. That way VACUUM
will have a decent chance of finishing off all required processing for
the index (and for the
nbtree VACUUM: cope with right sibling link corruption.
Avoid "right sibling's left-link doesn't match" errors when vacuuming a
corrupt nbtree index. Just LOG the issue and press on. That way VACUUM
will have a decent chance of finishing off all required processing for
the index (and for the
nbtree VACUUM: cope with right sibling link corruption.
Avoid "right sibling's left-link doesn't match" errors when vacuuming a
corrupt nbtree index. Just LOG the issue and press on. That way VACUUM
will have a decent chance of finishing off all required processing for
the index (and for the
nbtree VACUUM: cope with right sibling link corruption.
Avoid "right sibling's left-link doesn't match" errors when vacuuming a
corrupt nbtree index. Just LOG the issue and press on. That way VACUUM
will have a decent chance of finishing off all required processing for
the index (and for the
nbtree VACUUM: cope with right sibling link corruption.
Avoid "right sibling's left-link doesn't match" errors when vacuuming a
corrupt nbtree index. Just LOG the issue and press on. That way VACUUM
will have a decent chance of finishing off all required processing for
the index (and for the
nbtree VACUUM: cope with right sibling link corruption.
Avoid "right sibling's left-link doesn't match" errors when vacuuming a
corrupt nbtree index. Just LOG the issue and press on. That way VACUUM
will have a decent chance of finishing off all required processing for
the index (and for the
Fix filtering of "cloned" outer-join quals some more.
We've had multiple issues with the clause_is_computable_at logic that
I introduced in 2489d76c4: it's been known to accept more than one
clone of the same qual at the same plan node, and also to accept no
clones at all. It's looking
doc: fix typo in language tag documentation
Commit 1e16af8ab5 accidentally mistyped 'language' in one place.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/913b3da6aeda3f887b8796d8098d7227d32580b9
Modified Files
--
doc/src/sgml/charset.sgml | 2 +-
1
doc: Fix example query for pg_walinspect
The LIMIT clause had ended up in the wrong place in the query.
Backpatch to v15 where pg_walinspect was introduced.
Reported-by: Jian He
Discussion:
https://postgr.es/m/cacjufxhqxdr4nnmwmr6peivpag54j0dgwmuyqzrh5bx6+nt...@mail.gmail.com
doc: Fix example query for pg_walinspect
The LIMIT clause had ended up in the wrong place in the query.
Backpatch to v15 where pg_walinspect was introduced.
Reported-by: Jian He
Discussion:
https://postgr.es/m/cacjufxhqxdr4nnmwmr6peivpag54j0dgwmuyqzrh5bx6+nt...@mail.gmail.com
Fix pgbench in prepared mode with an empty pipeline
It crashes because it references memory that's not allocated in that
particular case. Fix by allocating it.
Reported-by: Alexander Lakhin
Discussion: https://postgr.es/m/bcf802a6-afc1-95b9-7bf4-c5dd868ec...@gmail.com
Branch
--
master
Fix pgbench in prepared mode with an empty pipeline
It crashes because it references memory that's not allocated in that
particular case. Fix by allocating it.
Reported-by: Alexander Lakhin
Discussion: https://postgr.es/m/bcf802a6-afc1-95b9-7bf4-c5dd868ec...@gmail.com
Branch
--
Fix typo in TAP tests of vacuumdb
Noticed while scanning the area, introduced in 582edc3.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/ecb968e7e3da69a39d3efab69fa63fe6c8d04b5f
Modified Files
--
src/bin/scripts/t/100_vacuumdb.pl | 2 +-
1 file
14 matches
Mail list logo
