Re: Index Administration: pg_index vs. pg_get_indexdef()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com>
Cc: PgSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Index Administration: pg_index vs. pg_get_indexdef()
Date: 2005-11-23 04:56:08
Message-ID: 10601.1132721768@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Thomas F. O'Connell" <tfo(at)sitening(dot)com> writes:
> In an old thread <http://archives.postgresql.org/pgsql-admin/2004-01/
> msg00271.php>, Tom Lane suggested that it would be "unreasonable" to
> use pg_index to reconstruct (expressional) indexes (in 7.4). The
> suggested alternative was to use pg_get_indexdef().

IIRC, the point I was trying to make was that making client code try to
interpret the contents of pg_index.indexprs or pg_index.indpred is a
losing proposition. If you feel that you'd rather read the other fields
of pg_index for yourself, I won't argue with you.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrew J. Kopciuch 2005-11-23 05:08:28 Re: tsearch2: more than one index per table?
Previous Message Tom Lane 2005-11-23 04:50:42 Re: Why pgAdmin III guru suggests VACUUM in 8.1