Remove pg_am.amindexnulls?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Remove pg_am.amindexnulls?
Date: 2011-01-08 01:08:38
Message-ID: 20234.1294448918@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Now that GIN can index null items, its amindexnulls flag in pg_am really
ought to be set true. However, looking at the usage of that column,
I wonder whether we shouldn't just delete it instead. The only present
usage is a rather convoluted test in CLUSTER to see if the index is
safely clusterable --- and AFAICS that test has been obsoleted anyhow
by the later addition of pg_am.amclusterable. Anyone against
simplifying matters by getting rid of pg_am.amindexnulls?

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2011-01-08 01:12:01 Re: Remove pg_am.amindexnulls?
Previous Message Tom Lane 2011-01-08 00:19:30 Re: Fixing GIN for empty/null/full-scan cases