pgsql: Change the reloptions machinery to use a table-based parser, and - Mailing list pgsql-committers

From alvherre@postgresql.org (Alvaro Herrera)
Subject pgsql: Change the reloptions machinery to use a table-based parser, and
Date
Msg-id 20090105171428.77B29754A17@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Change the reloptions machinery to use a table-based parser, and provide
a more complete framework for writing custom option processing routines
by user-defined access methods.

Catalog version bumped due to the general API changes, which are going to
affect user-defined "amoptions" routines.

Modified Files:
--------------
    pgsql/src/backend/access/common:
        reloptions.c (r1.12 -> r1.13)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/common/reloptions.c?r1=1.12&r2=1.13)
    pgsql/src/backend/access/gin:
        ginutil.c (r1.19 -> r1.20)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginutil.c?r1=1.19&r2=1.20)
    pgsql/src/backend/access/gist:
        gistutil.c (r1.32 -> r1.33)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gistutil.c?r1=1.32&r2=1.33)
    pgsql/src/backend/access/hash:
        hashutil.c (r1.58 -> r1.59)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hashutil.c?r1=1.58&r2=1.59)
    pgsql/src/backend/access/nbtree:
        nbtutils.c (r1.92 -> r1.93)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtutils.c?r1=1.92&r2=1.93)
    pgsql/src/include/access:
        reloptions.h (r1.6 -> r1.7)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/reloptions.h?r1=1.6&r2=1.7)
    pgsql/src/include/catalog:
        catversion.h (r1.516 -> r1.517)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h?r1=1.516&r2=1.517)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Add a --role option to pg_dump, pg_dumpall, and pg_restore.
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix an oversight in the function-default-arguments patch: after