Prevent archive recovery from scanning non-existent WAL files.
Previously when there were multiple timelines listed in the history file
of the recovery target timeline, archive recovery searched all of them,
starting from the newest timeline to the oldest one, to find the segment
to read. That is,
Prevent archive recovery from scanning non-existent WAL files.
Previously when there were multiple timelines listed in the history file
of the recovery target timeline, archive recovery searched all of them,
starting from the newest timeline to the oldest one, to find the segment
to read. That is,
Prevent archive recovery from scanning non-existent WAL files.
Previously when there were multiple timelines listed in the history file
of the recovery target timeline, archive recovery searched all of them,
starting from the newest timeline to the oldest one, to find the segment
to read. That is,
Prevent archive recovery from scanning non-existent WAL files.
Previously when there were multiple timelines listed in the history file
of the recovery target timeline, archive recovery searched all of them,
starting from the newest timeline to the oldest one, to find the segment
to read. That is,
Prevent archive recovery from scanning non-existent WAL files.
Previously when there were multiple timelines listed in the history file
of the recovery target timeline, archive recovery searched all of them,
starting from the newest timeline to the oldest one, to find the segment
to read. That is,
Hello,
On 2020-May-08, Alvaro Herrera wrote:
> Rework XLogReader callback system
I think this commit is causing buildfarm members bowerbird to crash, but
it's not getting any backtrace. Is it perchance possible to enable
whatever buildfarm feature it is that reports backtraces from crashes?
Tha
pg_restore: Provide file name with one failure message
Almost all error messages already include file name where relevant, but
this one had been overlooked. Repair.
Backpatch to 9.5.
Author: Euler Taveira
Discussion:
https://postgr.es/m/cah503wa_vorckl_43p9atrejcdymoz8mzfk9s6tjrqqbqne...@mail
pg_restore: Provide file name with one failure message
Almost all error messages already include file name where relevant, but
this one had been overlooked. Repair.
Backpatch to 9.5.
Author: Euler Taveira
Discussion:
https://postgr.es/m/cah503wa_vorckl_43p9atrejcdymoz8mzfk9s6tjrqqbqne...@mail
pg_restore: Provide file name with one failure message
Almost all error messages already include file name where relevant, but
this one had been overlooked. Repair.
Backpatch to 9.5.
Author: Euler Taveira
Discussion:
https://postgr.es/m/cah503wa_vorckl_43p9atrejcdymoz8mzfk9s6tjrqqbqne...@mail
pg_restore: Provide file name with one failure message
Almost all error messages already include file name where relevant, but
this one had been overlooked. Repair.
Backpatch to 9.5.
Author: Euler Taveira
Discussion:
https://postgr.es/m/cah503wa_vorckl_43p9atrejcdymoz8mzfk9s6tjrqqbqne...@mail
pg_restore: Provide file name with one failure message
Almost all error messages already include file name where relevant, but
this one had been overlooked. Repair.
Backpatch to 9.5.
Author: Euler Taveira
Discussion:
https://postgr.es/m/cah503wa_vorckl_43p9atrejcdymoz8mzfk9s6tjrqqbqne...@mail
pg_restore: Provide file name with one failure message
Almost all error messages already include file name where relevant, but
this one had been overlooked. Repair.
Backpatch to 9.5.
Author: Euler Taveira
Discussion:
https://postgr.es/m/cah503wa_vorckl_43p9atrejcdymoz8mzfk9s6tjrqqbqne...@mail
First-draft release notes for 12.3.
As usual, the release notes for other branches will be made by cutting
these down, but put them up for community review first.
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/ac0e30e0d0fe402fbdb3099fd8b32e4bc6755a6a
Modifi
Rework XLogReader callback system
Code review for 0dc8ead46363, prompted by a bug closed by 91c40548d5f7.
XLogReader's system for opening and closing segments had gotten too
complicated, with callbacks being passed at both the XLogReaderAllocate
level (read_page) as well as at the WALRead level (
Improve use of prepositions in messages
*in* database, *in* cluster, *on* server; and some related fixes
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/871696ba20e0251e86041576373809d1c7ca161d
Modified Files
--
src/bin/pg_dump/pg_dump.c | 4 ++--
Unify find_other_exec() error messages
There were a few different ways to line-wrap the error messages. Make
them all the same, and use placeholders for the actual program names,
to save translation work.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/7666ef313dcc
Fix several DDL issues of generated columns versus inheritance
Several combinations of generated columns and inheritance in CREATE
TABLE were not handled correctly. Specifically:
- Disallow a child column specifying a generation expression if the
parent column is a generated column. The child
Fix several DDL issues of generated columns versus inheritance
Several combinations of generated columns and inheritance in CREATE
TABLE were not handled correctly. Specifically:
- Disallow a child column specifying a generation expression if the
parent column is a generated column. The child
Propagate ALTER TABLE ... SET STORAGE to indexes
When creating a new index, the attstorage setting of the table column
is copied to regular (non-expression) index columns. But a later
ALTER TABLE ... SET STORAGE is not propagated to indexes, thus
creating an inconsistent and undumpable state.
Di
Propagate ALTER TABLE ... SET STORAGE to indexes
When creating a new index, the attstorage setting of the table column
is copied to regular (non-expression) index columns. But a later
ALTER TABLE ... SET STORAGE is not propagated to indexes, thus
creating an inconsistent and undumpable state.
Di
20 matches
Mail list logo
