From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Disallow the combination VACUUM FULL FREEZE for safety's sake, |
Date: | 2004-12-02 19:28:49 |
Message-ID: | 20041202192849.B527B3A5805@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
Disallow the combination VACUUM FULL FREEZE for safety's sake, for the
reasons I outlined in pghackers a few days ago.
Also, undo someone's overly optimistic decision to reduce tuple state
checks from if (...) elog() to Asserts. If I trusted this code more,
I might think it was a good idea to disable these checks in production
installations. But I don't.
Modified Files:
--------------
pgsql/doc/src/sgml:
manage-ag.sgml (r2.36 -> r2.37)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/manage-ag.sgml.diff?r1=2.36&r2=2.37)
pgsql/doc/src/sgml/ref:
vacuum.sgml (r1.35 -> r1.36)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/vacuum.sgml.diff?r1=1.35&r2=1.36)
pgsql/src/backend/commands:
vacuum.c (r1.296 -> r1.297)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuum.c.diff?r1=1.296&r2=1.297)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-12-02 19:32:58 | pgsql: Add: > * Allow a warm standby system to also allow read-only |
Previous Message | Bruce Momjian | 2004-12-02 18:13:48 | pgsql: Add: > * Fix psql's display of schema information (Neil) |