Skip site navigation (1) Skip section navigation (2)

pgsql: Make REINDEX DATABASE do what one would expect, namely reindex

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Make REINDEX DATABASE do what one would expect, namely reindex
Date: 2005-06-22 21:14:34
Message-ID: 20050622211434.36D1F52972@svr1.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Log Message:
-----------
Make REINDEX DATABASE do what one would expect, namely reindex all indexes
in the database.  The old behavior (reindex system catalogs only) is now
available as REINDEX SYSTEM.  I did not add the complementary REINDEX USER
case since there did not seem to be consensus for this, but it would be
trivial to add later.  Per recent discussions.

Modified Files:
--------------
    pgsql/doc/src/sgml:
        maintenance.sgml (r1.44 -> r1.45)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/maintenance.sgml.diff?r1=1.44&r2=1.45)
    pgsql/doc/src/sgml/ref:
        reindex.sgml (r1.26 -> r1.27)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/reindex.sgml.diff?r1=1.26&r2=1.27)
    pgsql/src/backend/commands:
        indexcmds.c (r1.132 -> r1.133)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/indexcmds.c.diff?r1=1.132&r2=1.133)
    pgsql/src/backend/nodes:
        copyfuncs.c (r1.307 -> r1.308)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/copyfuncs.c.diff?r1=1.307&r2=1.308)
        equalfuncs.c (r1.244 -> r1.245)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/equalfuncs.c.diff?r1=1.244&r2=1.245)
    pgsql/src/backend/parser:
        gram.y (r2.495 -> r2.496)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y.diff?r1=2.495&r2=2.496)
        keywords.c (r1.157 -> r1.158)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/keywords.c.diff?r1=1.157&r2=1.158)
    pgsql/src/backend/tcop:
        utility.c (r1.237 -> r1.238)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/utility.c.diff?r1=1.237&r2=1.238)
    pgsql/src/bin/psql:
        common.c (r1.103 -> r1.104)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/common.c.diff?r1=1.103&r2=1.104)
        tab-complete.c (r1.132 -> r1.133)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/tab-complete.c.diff?r1=1.132&r2=1.133)
    pgsql/src/include/commands:
        defrem.h (r1.64 -> r1.65)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/commands/defrem.h.diff?r1=1.64&r2=1.65)
    pgsql/src/include/nodes:
        parsenodes.h (r1.282 -> r1.283)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/parsenodes.h.diff?r1=1.282&r2=1.283)

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-06-22 21:23:29
Subject: Re: pg_terminate_backend idea
Previous:From: Chris CampbellDate: 2005-06-22 21:08:17
Subject: Re: Problem with dblink regression test

pgsql-committers by date

Next:From: Tom LaneDate: 2005-06-22 22:56:29
Subject: pgsql: Remove contrib modules that have been agreed to be obsolete.
Previous:From: James William PyeDate: 2005-06-22 19:24:43
Subject: python - be: Make Postgres.Query more intuitive by using

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group