Wait for WAL summarization to catch up before creating .partial file.
When a standby is promoted, CleanupAfterArchiveRecovery() may decide
to rename the final WAL file from the old timeline by adding ".partial"
to the name. If WAL summarization is enabled and this file is renamed
before its
Wait for WAL summarization to catch up before creating .partial file.
When a standby is promoted, CleanupAfterArchiveRecovery() may decide
to rename the final WAL file from the old timeline by adding ".partial"
to the name. If WAL summarization is enabled and this file is renamed
before its
Fix indentation.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/c883453cb29cb40c1e59c3c54d159c5e744da8a9
Modified Files
--
src/backend/postmaster/walsummarizer.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Fix indentation.
Branch
--
REL_17_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/f2af1f4559ea74a6133ac36df3204c12e8d12ed3
Modified Files
--
src/backend/postmaster/walsummarizer.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Allow WAL summarization to back up when timeline changes.
The old code believed that it was not possible to switch timelines
without first replaying all of the WAL from the old timeline, but
that turns out to be false, as demonstrated by an example from Fujii
Masao. As a result, it assumed that
Allow WAL summarization to back up when timeline changes.
The old code believed that it was not possible to switch timelines
without first replaying all of the WAL from the old timeline, but
that turns out to be false, as demonstrated by an example from Fujii
Masao. As a result, it assumed that
will understand what has gone wrong.
Laurenz Albe and Robert Haas
Discussion:
https://postgr.es/m/5468641ad821dad7aa3b2d65bf843146443a1b68.ca...@cybertec.at
Branch
--
REL_17_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/de8b098ce567526e4da7d6e51cfe0fb132123ad7
Modified Files
will understand what has gone wrong.
Laurenz Albe and Robert Haas
Discussion:
https://postgr.es/m/5468641ad821dad7aa3b2d65bf843146443a1b68.ca...@cybertec.at
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/744ddc6c6a0fa5d4d6d0e187cadcc632daaefc0e
Modified Files
Initialize wal_level in the initial checkpoint record.
As per Coverity and Tom Lane, commit 402b586d0 (back-patched to v17
as 2b5819e2b) forgot to initialize this new structure member in this
code path.
Branch
--
master
Details
---
Initialize wal_level in the initial checkpoint record.
As per Coverity and Tom Lane, commit 402b586d0 (back-patched to v17
as 2b5819e2b) forgot to initialize this new structure member in this
code path.
Branch
--
REL_17_STABLE
Details
---
Remove grotty use of disable_cost for TID scan plans.
Previously, the code charged disable_cost for CurrentOfExpr, and then
subtracted disable_cost from the cost of a TID path that used
CurrentOfExpr as the TID qual, effectively disabling all paths except
that one. Now, we instead suppress
Add missing call to ConditionVariableCancelSleep().
After calling ConditionVariableSleep() or ConditionVariableTimedSleep()
one or more times, code is supposed to call ConditionVariableCancelSleep()
to remove itself from the waitlist. This code neglected to do so.
As far as I know, that had no
Add missing call to ConditionVariableCancelSleep().
After calling ConditionVariableSleep() or ConditionVariableTimedSleep()
one or more times, code is supposed to call ConditionVariableCancelSleep()
to remove itself from the waitlist. This code neglected to do so.
As far as I know, that had no
Do not summarize WAL if generated with wal_level=minimal.
To do this, we must include the wal_level in the first WAL record
covered by each summary file; so add wal_level to struct Checkpoint
and the payload of XLOG_CHECKPOINT_REDO and XLOG_END_OF_RECOVERY.
This, in turn, requires bumping
Do not summarize WAL if generated with wal_level=minimal.
To do this, we must include the wal_level in the first WAL record
covered by each summary file; so add wal_level to struct Checkpoint
and the payload of XLOG_CHECKPOINT_REDO and XLOG_END_OF_RECOVERY.
This, in turn, requires bumping
pgindent, because I forgot to do that.
Commit 065583cf460f980a182498941ac52810f709a897 should have
included these changes.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/b48f275f18d7da4f4863888ad047cbd699698880
Modified Files
--
Prevent summarizer hang when summarize_wal turned off and back on.
Before this commit, when the WAL summarizer started up or recovered
from an error, it would resume summarization from wherever it left
off. That was OK normally, but wrong if summarize_wal=off had been
turned off temporary,
Fix generate_union_paths for non-sortable types.
The previous logic would fail to set groupList when
grouping_is_sortable() returned false, which could cause queries
to return wrong answers when some columns were not sortable.
David Rowley, reviewed by Heikki Linnakangas and Álvaro Herrera.
Re-allow planner to use Merge Append to efficiently implement UNION.
This reverts commit 7204f35919b7e021e8d1bc9f2d76fd6bfcdd2070,
thus restoring 66c0185a3 (Allow planner to use Merge Append to
efficiently implement UNION) as well as the follow-on commits
d5d2205c8, 3b1a7eb28, 7487044d6.
Per
Doc: return 66c0185a3 to the release notes.
This reverts commit e1e83a71715f1c2f0717bb66e630ca3bda79b9c1.
Per further discussion on pgsql-release, we wish to ship beta1 with
that feature, and patch the bug, rather than shipping beta1 with
that feature reverted.
Branch
--
master
Details
Document that increasing max_connections uses more resources.
Roberto Mello
Discussion:
http://postgr.es/m/CAKz==bJBCWrvN77fmuZ2XqD3jazWEb=e80aa4yv9c9tq61y...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/8ba346283335f7ee5bac2e904c2daad49a204c7c
Minor fixes to pg_combinebackup and its documentation.
The --tablespace-mapping option was specified with required_argument
rather than no_argument, which is wrong. Since the actual argument
string passed to getopt_long() included "T:", the single-character
form of the option still worked, but
pg_combinebackup: Detect checksum mismatches and document limitation.
If not all backups have the same checksum status, but the final backup
has checksums enabled, then the output directory may include pages
with invalid checksums. Document this limitation and explain how to
work around it.
In a
Try again to add test coverage for pg_combinebackup w/tablespaces.
My previous attempt to add this had to be reverted in commit
82023d47de9e262730b1f9b4ea77fae201a89d0a. I've revised the problematic
code a bit; hopefully it is OK now.
Discussion:
Revert recent ill-advised test case changes.
Commit 6bf5c42b5546984df29289918f952e6211069c54 cannot work on Windows,
because it lacks symlink support. While the bug fix in commit
cd64dc42d1e1b03e57e6ba3d316e4f9dec52a78d is correct as far as I know,
the test case changes depend on the previous
Use tempdir_short instead of tempdir.
After cd64dc42d1e1b03e57e6ba3d316e4f9dec52a78d, a significant
percentage of the buildfarm got unhappy, because pg_basebackup chokes
if it tries to create a tarfile with symlink more than 99 characters
in length. To try to fix that problem, use tempdir_short
pg_combinebackup: Fix incorrect tablespace handling.
The previous coding mangled the pathname calculation for
incremental files located in user-defined tablespaces.
Enhance the test cases to cover such cases, as I should have
done originally. Thanks to Andres Freund for alerting me to the
lack
Make PostgreSQL::Test::Cluster::init_from_backup handle tablespaces.
This commit doesn't use this infrastructure for anything new, although
it does adapt 010_pg_basebackup.pl to use it. However, a future commit
will use this to improve test coverage for pg_combinebackup.
Patch by me, reviewed
Remove spurious "the".
Spotted by Martin Marqués.
Discussion:
http://postgr.es/m/cabeg9lvqmtskrokhca_mkju1duarw4v+smejkurygjpvbzf...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/fbed6ebe41beb72d9b7978a414ed4e8515ed1b19
Modified Files
Restrict where INCREMENTAL.${NAME} files are recognized.
Previously, they were recognized anywhere in an incremental backup
directory; now, we restrict this to places where they are expected to
appear. That means this code will need updating if we ever do
incremental backups of files in other
docs: Mention that pg_combinebackup does not verify backups.
We don't want users to think that pg_combinebackup is trying to check
the validity of individual backups, because it isn't. Adjust the wording
about sanity checks to make it clear that verification of individual
backups is the job of
docs: Consolidate into new "WAL for Extensions" chapter.
Previously, we had consecutive, very short chapters called "Generic
WAL" and "Custom WAL Resource Managers," explaining different approaches
to the same problem. Merge them into a single chapter. Explain most
of the differences between the
Fix incorrect calculation in BlockRefTableEntryGetBlocks.
The previous formula was incorrect in the case where the function's
nblocks argument was a multiple of BLOCKS_PER_CHUNK, which happens
whenever a relation segment file is exactly 512MB or exactly 1GB in
length. In such cases, the formula
docs: Merge separate chapters on built-in index AMs into one.
The documentation index is getting very long, which makes it hard
to find things. Since these chapters are all very similar in structure
and content, merging them is a natural way of reducing the size of
the toplevel index.
Rather
Remove reachable call to pg_unreachable().
The loop just before this uses break, not return, so this line
is reachable. Commit cafe1056558fe07cdc52b95205588fcd80870362
introduced this issue.
Jelte Fennema-Nio, reviewed by Tristan Partin
Discussion:
Fix old, misleading comment for PGRES_POLLING_ACTIVE.
The comment implies that we can eventually remove this, but per
discussion, we actually don't want to do that ever, in order to
maintain compatibility.
Jelte Fennema-Nio, reviewed by Tristan Partin
Discussion:
docs: Demote "Monitoring Disk Usage" from chapter to section.
This chapter is very short, and the immediately preceding chapter is
called "Monitoring Database Activity". So, instead of having a
separate chapter for this, make it the last section of the preceding
chapter instead.
Discussion:
On Tue, Apr 2, 2024 at 5:40 PM Alexander Korotkov wrote:
> This appears to have missing pgindent.
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=koel=2024-04-02%2021%3A19%3A02
Argh, sorry. I think someone else fixed this.
--
Robert Haas
EDB: http://www.enterprisedb.com
Allow SIGINT to cancel psql database reconnections.
After installing the SIGINT handler in psql, SIGINT can no longer cancel
database reconnections. For instance, if the user starts a reconnection
and then needs to do some form of interaction (ie psql is polling),
there is no way to cancel the
Expose PQsocketPoll via libpq
This is useful when connecting to a database asynchronously via
PQconnectStart(), since it handles deciding between poll() and
select(), and some of the required boilerplate.
Tristan Partin, reviewed by Gurjeet Singh, Heikki Linnakangas, Jelte
Fennema-Nio, and me.
On Fri, Mar 29, 2024 at 9:03 AM Jelte Fennema-Nio wrote:
> no worries, these things happen. I'm just glad it's committed and I
> can now focus on different things than back and forth discussion over
> documentation that all looks pretty much identical to me.
Yeah, imagine that!
--
Ro
Oh no! Jelte, I'm so sorry ... I spelled your name wrong in this
commit message. :-(
Please accept my apologies.
...Robert
On Fri, Mar 29, 2024 at 8:45 AM Robert Haas wrote:
>
> Add allow_alter_system GUC.
>
> This is marked PGC_SIGHUP, so it can only be set in a configur
Add allow_alter_system GUC.
This is marked PGC_SIGHUP, so it can only be set in a configuration
file, not anywhere else; and it is also marked GUC_DISALLOW_IN_AUTO_FILE,
so it can't be set using ALTER SYSTEM. When set to false, the
ALTER SYSTEM command is disallowed.
There was considerable
Rename COMPAT_OPTIONS_CLIENT to COMPAT_OPTIONS_OTHER.
The user-facing name is "Other Platforms and Clients", but the
internal name seems too focused on clients specifically, especially
given the plan to add a new setting to this session that is about
platform or deployment model compatibility
docs: Make claims about the benefits of HOT updates more precise.
The old text claims that HOT completely removes old row versions.
It was unclear whether it just meant the tuples themselves, or the
tuples together with their line pointers. If it meant the former,
it was wrong because we can
the
semantics of no-wait that strictly.
Robert Haas and Jingxian Li
Discussion:
http://postgr.es/m/ca+tgmobch-kmxgvpb0bb-inmdtcnktvcz4jbxdjows3kym+...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/2346df6fc373df9c5ab944eebecf7d3036d727de
Modified Files
Add the system identifier to backup manifests.
Before this patch, if you took a full backup on server A and then
tried to use the backup manifest to take an incremental backup on
server B, it wouldn't know that the manifest was from a different
server and so the incremental backup operation could
to the control file itself.
Amul Sul and Robert Haas, reviewed by Michael Paquier
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/dbfc44716596073b99e093a04e29e774a518f520
Modified Files
--
src/bin/pg_combinebackup/pg_combinebackup.c | 2 +-
src/common
pg_verifybackup: Refactor parse_manifest_file.
Return a pointer to the manifest_data instead of individual pointers
to relevant data stored within the manifest_data object. The previous
approach scales poorly if we add more things to the backup manifest,
as has been proposed.
Amul Sul, reviewed
Fix pgindent damage.
Apparently, I neglected to pgindent the prior commit.
Per buildfarm.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/dd7ea37c435e10f9c5aa3fb257a05c08814a4ad2
Modified Files
--
src/backend/backup/basebackup_incremental.c | 4 ++--
Fix incremental backup interaction with XLOG_DBASE_CREATE_FILE_COPY.
After XLOG_DBASE_CREATE_FILE_COPY, a correct incremental backup needs
to copy in full everything with the database and tablespace OID
mentioned in that record; but that record doesn't specifically mention
the blocks, or even the
Continue my quest to make 002_blocks.pl pass reliably.
The latest buildfarm failures show that after the insert, we don't
actually wait long enough for WAL summarization to catch up, apparently
because the on disk state gets updated before the in-memory state, and
so by checking the on disk state
n/show_log.pl?nm=koel=2024-01-28%2016%3A19%3A03
>
> I think we should as we don't know how long it'll be before this gets
> reverted. In the meantime, having a buildfarm member red is annoying.
I included a fix for this in ea18eb7d625573dc369df619f7ff3b9e60e47531.
Apologies for the incon
In 002_blocks.pl, try to prevent a HOT update.
Make the new tuple larger than the old one so that it, hopefully, won't
manage to squeeze into leftover freespace on the same page. The test
is trying to verify that the UPDATE touches 2 pages, but if a HOT
update happens, then it doesn't.
Per
Revise pg_walsummary's 002_blocks test to avoid spurious failures.
Analysis of buildfarm results showed that the code that was intended
to wait for the inserts performed by this test to complete did not
actually do so. Try to make that logic more robust.
Improve error checking elsewhere in the
Temporary patch to help debug pg_walsummary test failures.
The tests in 002_blocks.pl are failing in the buildfarm from time to
time, but we don't know how to reproduce the failure elsewhere. The
most obvious explanation seems to be the unexpected disappearance of a
WAL summary file, so bump up
combining the FSM updates, simplify the logic for calling
lazy_scan_new_or_empty() and lazy_scan_noprune().
Also update a few comemnts in this part of the code to make them,
hopefully, clearer.
Melanie Plageman and Robert Haas
Discussion:
https://postgr.es/m/CA%2BTgmoaLTvipm%3Dxx4rJLr07m908PCu
Remove LVPagePruneState.
Commit cb970240f13df2b63f0410f81f452179a2b78d6f moved some code from
lazy_scan_heap() to lazy_scan_prune(), and now some things that used to
need to be passed back and forth are completely local to lazy_scan_prune().
Hence, this struct is mostly obsolete. The only thing
Move VM update code from lazy_scan_heap() to lazy_scan_prune().
Most of the output parameters of lazy_scan_prune() were being
used to update the VM in lazy_scan_heap(). Moving that code into
lazy_scan_prune() simplifies lazy_scan_heap() and requires less
communication between the two.
This
Clarify language in incremental backup glossary entry.
These changes were intended to be included in commit
7b1dbf0a8d1d4e1e6d01a76dc45a3216e8a16d94, but I goofed.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/0a157a4d441586a0e590e2f8a3839114e01df4b7
Modified
Optimize vacuuming of relations with no indexes.
If there are no indexes on a relation, items can be marked LP_UNUSED
instead of LP_DEAD when pruning. This significantly reduces WAL
volume, since we no longer need to emit one WAL record for pruning
and a second to change the LP_DEAD line pointers
More documentation updates for incremental backup.
Add new terms to glossary. Add a reference to walsummarizer
to monitoring.sgml.
Matthias van de Meent and Robert Haas
Discussion:
http://postgr.es/m/caeze2wjhdvcqee_qqeok3na6dwudogsbjaxzmydaqiaah1u...@mail.gmail.com
Branch
--
master
Be more consistent about whether to update the FSM while vacuuming.
Previously, when lazy_scan_noprune() was called and returned true, we would
update the FSM immediately if the relation had no indexes or if the page
contained no dead items. On the other hand, when lazy_scan_prune() was
called,
Fix typos.
Alexander Lakhin
Discussion: http://postgr.es/m/212b0987-83e5-e2ae-c5e8-b8170fdaf...@gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/237d01139b8a2ad26036d9025ae8e8e99b53e08c
Modified Files
--
doc/src/sgml/func.sgml
On Thu, Jan 11, 2024 at 1:49 PM Robert Haas wrote:
> On Thu, Jan 11, 2024 at 12:56 PM Robert Haas wrote:
> > Add new pg_walsummary tool.
>
> culicidae is unhappy with this, but I don't yet understand why. The output is:
>
> # Failed test 'stdout shows block 0 modified'
>
On Thu, Jan 11, 2024 at 12:56 PM Robert Haas wrote:
> Add new pg_walsummary tool.
culicidae is unhappy with this, but I don't yet understand why. The output is:
# Failed test 'stdout shows block 0 modified'
# at t/002_blocks.pl line 85.
# 'TS 1663, DB 5, REL 16384, F
Fix typo.
Noriyoshi Shinoda
Discussion:
http://postgr.es/m/dm4pr84mb17347d9466419413698105d8ee...@dm4pr84mb1734.namprd84.prod.outlook.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/882887e9b458f533b301c36951c93dfdd37dccfc
Modified Files
--
Try to fix pg_walsummary buildfarm failures.
Apparently the new tuple isn't guaranteed to end up at the end of
the relation, so make the test not depend on that happening.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/a7097ca630a25dd2248229f21ebce4968d85d10a
Remove hastup from LVPagePruneState.
Instead, just have lazy_scan_prune() and lazy_scan_noprune() update
LVRelState->nonempty_pages directly. This makes the two functions
more similar and also removes makes lazy_scan_noprune need one fewer
output parameters.
Melanie Plageman, reviewed by Andres
Reindent after commit d9ef650fca7bc574586f4171cd929cfd5240326e.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/5faffa0434b484772782ff4763c0b2080222dde0
Modified Files
--
src/backend/postmaster/walsummarizer.c | 2 +-
1 file changed, 1 insertion(+), 1
Repair various defects in dc212340058b4e7ecfc5a7a81ec50e7a207bf288.
pg_combinebackup had various problems:
* strncpy was used in various places where strlcpy should be used
instead, to avoid any possibility of the result not being
\0-terminated.
* scan_for_existing_tablespaces() failed to
Add new pg_walsummary tool.
This can dump the contents of the WAL summary files found in
pg_wal/summaries. Normally, this shouldn't really be something anyone
needs to do, but it may be needed for debugging problems with
incremental backup, or could possibly be useful to external tools.
Add new function pg_get_wal_summarizer_state().
This makes it possible to access information about the progress
of WAL summarization from SQL. The previously-added functions
pg_available_wal_summaries() and pg_wal_summary_contents() only
examine on-disk state, but this function exposes
Document WAL summarization information functions.
Commit 174c480508ac25568561443e6d4a82d5c1103487 added two new
information functions but failed to document them anywhere.
Discussion:
http://postgr.es/m/CA+Tgmobvqqj-DW9F7uUzT-cQqs6wcVb-Xhs=w=hzjnxse-k...@mail.gmail.com
Branch
--
master
Fix defects in PrepareForIncrementalBackup.
Swap the arguments to TimestampDifferenceMilliseconds so that we get
a positive answer instead of zero.
Then use the result of that computation instead of ignoring it.
Per reports from Alexander Lakhin.
Discussion:
Remove Lock suffix from WALSummarizerLock in wait_event_names.txt
Nathan Bossart
Discussion: https://postgr.es/m/20240102173120.GA1061678@nathanxps13
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/371b07e8944983261a0f73c3b52dbbf0fd076a96
Modified Files
libpq: fix typo "occurences" -> "occurrences" in tests
Dagfinn Ilmari Mannsåker, reviewed by Shubham Khanna.
Discussion: http://postgr.es/m/87le9fmi01@wibble.ilmari.org
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/ff09129bec28028c57eb263cbca2836f42c2256c
tsquery: fix typo "rewrited" -> "rewritten"
Dagfinn Ilmari Mannsåker, reviewed by Shubham Khanna.
Discussion: http://postgr.es/m/87le9fmi01@wibble.ilmari.org
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/591cf626e71b460c53bef23347b93a0cfbd91f0f
Modified
jsonpath_exec: fix typo "absense" -> "absence"
Dagfinn Ilmari Mannsåker, reviewed by Shubham Khanna.
Discussion: http://postgr.es/m/87le9fmi01@wibble.ilmari.org
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/5bc7b33b4e16d02fc21b493649939e438b071850
Modified
gist: fix typo "split(t)ed" -> "split"
Dagfinn Ilmari Mannsåker, reviewed by Shubham Khanna.
Discussion: http://postgr.es/m/87le9fmi01@wibble.ilmari.org
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/e62e73f3a2f2af765a3c69486ed78a5bc451367e
Modified Files
Fix typos in comments and in one isolation test.
Dagfinn Ilmari Mannsåker, reviewed by Shubham Khanna. Some subtractions
by me.
Discussion: http://postgr.es/m/87le9fmi01@wibble.ilmari.org
Branch
--
master
Details
---
Add WALSummarizerLock to wait_event_names.txt
Per report from Nathan Bossart.
Discussion: http://postgr.es/m/20231227153647.GA601861@nathanxps13
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/5c430f9dc559ecd3bda8bebf4854f3f8d8bd86f3
Modified Files
--
Initialize variable to placate compiler.
I don't think there's a real problem here, because if we reach
the loop over 'tles' then we will either find at least one
TimeLineHistoryEntry such that oldest_segno != 0, in which case
unsummarized_lsn will be initialized, or else unsummarized_tli
will
Replace nonsense comment with a relevant one.
Per report from Alexander Lakhin.
Discussion: http://postgr.es/m/061cccf7-0cac-804f-4c2a-9d6da8e38...@gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/ffc6ab9b56ae02a64349c8c6b59dd659dab5516a
Modified Files
Fix numerous typos in incremental backup commits.
Apparently, spell check would have been a really good idea.
Alexander Lakhin, with a few additions as per an off-list report
from Andres Freund.
Discussion: http://postgr.es/m/f08f7c60-1ad3-0b57-d580-54b11f07c...@gmail.com
Branch
--
master
On Wed, Dec 20, 2023 at 10:35 AM Andrew Dunstan wrote:
> Yeah, the commit removed our dummy version of Win32/Registry.pm. I have
> disabled the test for that file on branches later than 16, and koel and
> crake are back to green.
Great, thanks for the quick work.
--
Robert Haas
Add support for incremental backup.
To take an incremental backup, you use the new replication command
UPLOAD_MANIFEST to upload the manifest for the prior backup. This
prior backup could either be a full backup or another incremental
backup. You then use BASE_BACKUP with the INCREMENTAL option
rl5) at ./src/tools/win32tzlist.pl line
21.
BEGIN failed--compilation aborted at ./src/tools/win32tzlist.pl line 21.
win32tzlist.pl still says "use Win32::Registry" but the commit removed
src/tools/msvc/dummylib/Win32/Registry.pm.
--
Robert Haas
EDB: http://www.enterprisedb.com
Add a new WAL summarizer process.
When active, this process writes WAL summary files to
$PGDATA/pg_wal/summaries. Each summary file contains information for a
certain range of LSNs on a certain TLI. For each relation, it stores a
"limit block" which is 0 if a relation is created or destroyed
Move src/bin/pg_verifybackup/parse_manifest.c into src/common.
This makes it possible for the code to be easily reused by other
client-side tools, and/or by the server.
Patch by me. Review of this patch in particular by at least Peter
Eisentraut; reviewers for the patch series in general include
Fix brown paper bag bug in 5c47c6546c413d5eb51c1626070a807026e6139d.
The previous logic failed to work for anything other than the first
segment of a relation.
Report by Jakub Wartak. Patch by me.
Discussion:
http://postgr.es/m/cakzirmwd3ktnmqhm9bv4or_1umehxroo6kgyjqkiw9dfm8c...@mail.gmail.com
Rename pg_verifybackup's JsonManifestParseContext callback functions.
The old names were too generic, and would have applied to any binary
that made use of JsonManifestParseContext. Rename to make the names
specific to pg_verifybackup, since there are plans afoot to reuse
this infrastructure.
Rename JsonManifestParseContext callbacks.
There is no real reason to just run multiple words together when
we can instead punctuate them with marks intended for that purpose.
Per suggestion from Álvaro Herrera.
Discussion: http://postgr.es/m/202311161021.nisg7imt7kyf@alvherre.pgsql
Branch
Change how a base backup decides which files have checksums.
Previously, it thought that any plain file located under global, base,
or a tablespace directory had checksums unless it was in a short list
of excluded files. Now, it thinks that files in those directories have
checksums if
Change struct tablespaceinfo's oid member from 'char *' to 'Oid'
This shouldn't change behavior except in the unusual case where
there are file in the tablespace directory that have entirely
numeric names but are nevertheless not possible names for a
tablespace directory, either because their
Refactor parse_filename_for_nontemp_relation to parse more.
Instead of returning the number of characters in the RelFileNumber,
return the RelFileNumber itself. Continue to return the fork number,
as before, and additionally return the segment number.
parse_filename_for_nontemp_relation now
During online checkpoints, insert XLOG_CHECKPOINT_REDO at redo point.
This allows tools that read the WAL sequentially to identify (possible)
redo points when they're reached, rather than only being able to
detect them in retrospect when XLOG_CHECKPOINT_ONLINE is found, possibly
much later in the
for it.
Alexander Alekseev, John Naylor, Robert Haas, reviewed at various
times by Peter Geoghegan, Hannu Krosing, and Andres Freund.
Discussion:
http://postgr.es/m/ca+tgmozbg95fir9wvqpaxpgprkacst2okvge+pkppfppn7s...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg
Talk about assigning, rather than generating, new MultiXactIds.
The word "assign" is used in various places internally to describe what
GetNewMultiXactId does, but the user-facing messages have previously
said "generate". For consistency, standardize on "assign," which seems
(at least to me) to
of VACUUM failing in multi-user mode were much higher.
Alexander Alekseev, John Naylor, Robert Haas, reviewed at various
times by Peter Geoghegan, Hannu Krosing, and Andres Freund.
Discussion:
http://postgr.es/m/ca+tgmoytsudrzahcmjfhlztk1vev29mo_u-mt+xwhrbj_4n...@mail.gmail.com
Branch
1 - 100 of 734 matches
Mail list logo
