Log Message:
---
Force VACUUM to recalculate oldestXmin even when we haven't changed our
own database's datfrozenxid, if the current value is old enough to be
forcing autovacuums or warning messages. This ensures that a bogus
value is replaced as soon as possible. Per a comment from Heikk
Log Message:
---
Actually, we need to bump the format identifier on twophase files
because of readjustment of 2PC rmgr IDs for flatfile removal.
Modified Files:
--
pgsql/src/backend/access/transam:
twophase.c (r1.54 -> r1.55)
(http://anoncvs.postgresql.org/
Log Message:
---
Bump catversion for flat-file-ectomy. Also remove a missed dead extern
declaration.
Modified Files:
--
pgsql/src/include/catalog:
catversion.h (r1.537 -> r1.538)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversio
Log Message:
---
Remove flatfiles.c, which is now obsolete.
Recent commits have removed the various uses it was supporting. It was a
performance bottleneck, according to bug report #4919 by Lauris Ulmanis; seems
it slowed down user creation after a billion users.
Modified Files:
Log Message:
---
Move processing of startup-packet switches and GUC settings into InitPostgres,
to fix the problem that SetClientEncoding needs to be done before
InitializeClientEncoding, as reported by Zdenek Kotala. We get at least
the small consolation of being able to remove the bizarr
Heikki Linnakangas writes:
> 1. Cluster is close to the stop limit.
> 2. Autovacuum runs, updates pg_database and advances oldestXid. Phew!
> 3. Crash.
> After recovery, oldestXid is reset to the old value, and you start
> getting warnings again. However, everything seems fine in pg_database,
> a
Log Message:
---
Change the autovacuum launcher to read pg_database directly, rather than
via the "flat files" facility. This requires making it enough like a backend
to be able to run transactions; it's no longer an "auxiliary process" but
more like the autovacuum worker processes. Also,
Tom Lane wrote:
> Log Message:
> ---
> Track the current XID wrap limit (or more accurately, the oldest unfrozen
> XID) in checkpoint records. This eliminates the need to recompute the value
> from scratch during database startup, which is one of the two remaining
> reasons for the flatfil
