pg.ddx.io pgsql-committers@postgresql.org mailing list archive
help / color / mirror / Atom feedpgsql: Mention that tables have a visibility map fork alongside the main
4+ messages / 2 participants
[nested] [flat]
* pgsql: Mention that tables have a visibility map fork alongside the main
@ 2009-04-23 10:20 Heikki Linnakangas <heikki@postgresql.org>
0 siblings, 0 replies; 4+ messages in thread
From: heikki@postgresql.org @ 2009-04-23 10:20 UTC (permalink / raw)
To: pgsql-committers
Log Message:
-----------
Mention that tables have a visibility map fork alongside the main fork
and FSM.
Modified Files:
--------------
pgsql/doc/src/sgml:
storage.sgml (r1.26 -> r1.27)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/storage.sgml?r1=1.26&r2=1.27)
^ permalink raw reply [nested|flat] 4+ messages in thread
* pgsql: Handle interleavings between CREATE DATABASE steps and base back
@ 2024-02-01 21:46 Noah Misch <noah@leadboat.com>
0 siblings, 0 replies; 4+ messages in thread
From: Noah Misch @ 2024-02-01 21:46 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Handle interleavings between CREATE DATABASE steps and base backup.
Restoring a base backup taken in the middle of CreateDirAndVersionFile()
or write_relmap_file() would lose the function's effects. The symptom
was absence of the database directory, PG_VERSION file, or
pg_filenode.map. If missing the directory, recovery would fail. Either
missing file would not fail recovery but would render the new database
unusable. Fix CreateDirAndVersionFile() with the transam/README "action
first and then write a WAL entry" strategy. That has a side benefit of
moving filesystem mutations out of a critical section, reducing the ways
to PANIC. Fix the write_relmap_file() call with a lock acquisition, so
it interacts with checkpoints like non-CREATE DATABASE calls do.
Back-patch to v15, where commit 9c08aea6a3090a396be334cc58c511edab05776a
introduced STRATEGY=WAL_LOG and made it the default.
Discussion: https://postgr.es/m/20240130195003.0a.nmisch@google.com
Branch
------
REL_15_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/d493bed28f7f6c77051bba3dde383e0ff78d3a19
Modified Files
--------------
src/backend/commands/dbcommands.c | 44 +++++++++++++++----------------------
src/backend/utils/cache/relmapper.c | 16 ++++++++++++--
2 files changed, 32 insertions(+), 28 deletions(-)
^ permalink raw reply [nested|flat] 4+ messages in thread
* pgsql: Handle interleavings between CREATE DATABASE steps and base back
@ 2024-02-01 21:46 Noah Misch <noah@leadboat.com>
0 siblings, 0 replies; 4+ messages in thread
From: Noah Misch @ 2024-02-01 21:46 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Handle interleavings between CREATE DATABASE steps and base backup.
Restoring a base backup taken in the middle of CreateDirAndVersionFile()
or write_relmap_file() would lose the function's effects. The symptom
was absence of the database directory, PG_VERSION file, or
pg_filenode.map. If missing the directory, recovery would fail. Either
missing file would not fail recovery but would render the new database
unusable. Fix CreateDirAndVersionFile() with the transam/README "action
first and then write a WAL entry" strategy. That has a side benefit of
moving filesystem mutations out of a critical section, reducing the ways
to PANIC. Fix the write_relmap_file() call with a lock acquisition, so
it interacts with checkpoints like non-CREATE DATABASE calls do.
Back-patch to v15, where commit 9c08aea6a3090a396be334cc58c511edab05776a
introduced STRATEGY=WAL_LOG and made it the default.
Discussion: https://postgr.es/m/20240130195003.0a.nmisch@google.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/df220714e50f2e924c57f4a8d9f578cf6c92a73f
Modified Files
--------------
src/backend/commands/dbcommands.c | 44 +++++++++++++++----------------------
src/backend/utils/cache/relmapper.c | 16 ++++++++++++--
2 files changed, 32 insertions(+), 28 deletions(-)
^ permalink raw reply [nested|flat] 4+ messages in thread
* pgsql: Handle interleavings between CREATE DATABASE steps and base back
@ 2024-02-01 21:46 Noah Misch <noah@leadboat.com>
0 siblings, 0 replies; 4+ messages in thread
From: Noah Misch @ 2024-02-01 21:46 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Handle interleavings between CREATE DATABASE steps and base backup.
Restoring a base backup taken in the middle of CreateDirAndVersionFile()
or write_relmap_file() would lose the function's effects. The symptom
was absence of the database directory, PG_VERSION file, or
pg_filenode.map. If missing the directory, recovery would fail. Either
missing file would not fail recovery but would render the new database
unusable. Fix CreateDirAndVersionFile() with the transam/README "action
first and then write a WAL entry" strategy. That has a side benefit of
moving filesystem mutations out of a critical section, reducing the ways
to PANIC. Fix the write_relmap_file() call with a lock acquisition, so
it interacts with checkpoints like non-CREATE DATABASE calls do.
Back-patch to v15, where commit 9c08aea6a3090a396be334cc58c511edab05776a
introduced STRATEGY=WAL_LOG and made it the default.
Discussion: https://postgr.es/m/20240130195003.0a.nmisch@google.com
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/6d423e9ff95ac2e62655faa97633155d08dfdd64
Modified Files
--------------
src/backend/commands/dbcommands.c | 44 +++++++++++++++----------------------
src/backend/utils/cache/relmapper.c | 16 ++++++++++++--
2 files changed, 32 insertions(+), 28 deletions(-)
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2024-02-01 21:46 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2009-04-23 10:20 pgsql: Mention that tables have a visibility map fork alongside the main Heikki Linnakangas <heikki@postgresql.org>
2024-02-01 21:46 pgsql: Handle interleavings between CREATE DATABASE steps and base back Noah Misch <noah@leadboat.com>
2024-02-01 21:46 pgsql: Handle interleavings between CREATE DATABASE steps and base back Noah Misch <noah@leadboat.com>
2024-02-01 21:46 pgsql: Handle interleavings between CREATE DATABASE steps and base back Noah Misch <noah@leadboat.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox