Re: pgsql/ oc/src/sgml/bki.sgml oc/src/sgml/catalo ...

TODO updated.

> CVSROOT:    /home/projects/pgsql/cvsroot
> Module name:    pgsql
> Changes by:    tgl@hub.org    01/06/12 01:55:50
>
> Modified files:
>     doc/src/sgml   : bki.sgml catalogs.sgml
>     src/backend/access/common: heaptuple.c
>     src/backend/catalog: Makefile heap.c index.c indexing.c
>     src/backend/commands: async.c command.c dbcommands.c user.c
>     src/backend/storage/lmgr: lmgr.c
>     src/backend/utils/cache: relcache.c syscache.c
>     src/backend/utils/init: globals.c
>     src/bin/initdb : initdb.sh
>     src/include/access: heapam.h
>     src/include/catalog: catversion.h indexing.h pg_attrdef.h
>                          pg_attribute.h pg_class.h pg_listener.h
>                          pg_relcheck.h pg_trigger.h pg_type.h
>     src/include    : postgres.h
>     src/include/utils: syscache.h
>     src/test/regress/expected: opr_sanity.out sanity_check.out
>
> Log message:
>     Clean up various to-do items associated with system indexes:
>     pg_database now has unique indexes on oid and on datname.
>     pg_shadow now has unique indexes on usename and on usesysid.
>     pg_am now has unique index on oid.
>     pg_opclass now has unique index on oid.
>     pg_amproc now has unique index on amid+amopclaid+amprocnum.
>     Remove pg_rewrite's unnecessary index on oid, delete unused RULEOID syscache.
>     Remove index on pg_listener and associated syscache for performance reasons
>     (caching rows that are certain to change before you need 'em again is
>     rather pointless).
>     Change pg_attrdef's nonunique index on adrelid into a unique index on
>     adrelid+adnum.
>
>     Fix various incorrect settings of pg_class.relisshared, make that the
>     primary reference point for whether a relation is shared or not.
>     IsSharedSystemRelationName() is now only consulted to initialize relisshared
>     during initial creation of tables and indexes.  In theory we might now
>     support shared user relations, though it's not clear how one would get
>     entries for them into pg_class &etc of multiple databases.
>
>     Fix recently reported bug that pg_attribute rows created for an index all have
>     the same OID.  (Proof that non-unique OID doesn't matter unless it's
>     actually used to do lookups ;-))
>
>     There's no need to treat pg_trigger, pg_attrdef, pg_relcheck as bootstrap
>     relations.  Convert them into plain system catalogs without hardwired
>     entries in pg_class and friends.
>
>     Unify global.bki and template1.bki into a single init script postgres.bki,
>     since the alleged distinction between them was misleading and pointless.
>     Not to mention that it didn't work for setting up indexes on shared
>     system relations.
>
>     Rationalize locking of pg_shadow, pg_group, pg_attrdef (no need to use
>     AccessExclusiveLock where ExclusiveLock or even RowExclusiveLock will do).
>     Also, hold locks until transaction commit where necessary.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026