Re: Collation order for btree-indexable datatypes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Collation order for btree-indexable datatypes
Date: 2001-05-02 23:02:28
Message-ID: 17499.988844548@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> What parts of the changes would require an initdb, would new
> functions need to be added or the index ops need to change or would
> it be fixes to the existing functions (if the latter, wouldn't a recompile
> and dropping/recreating the indexes be enough?)

Yes, dropping and recreating any user indexes that contain the problematic
values would be sufficient to get you out of trouble. We don't need any
system catalog changes for this, AFAICS.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephan Szabo 2001-05-02 23:05:49 Re: Collation order for btree-indexable datatypes
Previous Message Stephan Szabo 2001-05-02 22:57:23 Re: Collation order for btree-indexable datatypes