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

pgsql: Remove pg_am.amindexnulls.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Remove pg_am.amindexnulls.
Date: 2011-01-08 21:08:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Remove pg_am.amindexnulls.

The only use we have had for amindexnulls is in determining whether an
index is safe to cluster on; but since the addition of the amclusterable
flag, that usage is pretty redundant.

In passing, clean up assorted sloppiness from the last patch that touched
pg_am.h: Natts_pg_am was wrong, and ambuildempty was not documented.



Modified Files
doc/src/sgml/catalogs.sgml       |   14 +++++-----
doc/src/sgml/indexam.sgml        |   12 ++++-----
src/backend/commands/cluster.c   |   37 ------------------------------
src/include/catalog/catversion.h |    2 +-
src/include/catalog/pg_am.h      |   46 ++++++++++++++++++-------------------
5 files changed, 35 insertions(+), 76 deletions(-)

pgsql-committers by date

Next:From: Michael MeskesDate: 2011-01-08 22:02:47
Subject: pgsql: In ecpg's parser removed a fixed length limit for constantsdefi
Previous:From: Tom LaneDate: 2011-01-08 19:48:48
Subject: pgsql: Refactor GIN's handling of duplicate search entries.

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