On Wed, Sep 4, 2013 at 11:02 PM, Quan Zongliang <quanzongli...@gmail.com> wrote: > I think of a new idea. > Add a compare method column to pg_collation. > Every collation has its own compare function or null. > When function varstr_cmp is called, if specified collation > has compare function, call it instead of strcoll().
I think we're going to need to have two kinds of collations: OS-derived collations (which get all of their smarts from the OS), and PG-internal collations (which use PG-aware code for everything). Which I suspect is a bit more involved than what you're imagining, but mixing and matching doesn't seem likely to end well. However, what you're proposing might serve as a useful demonstration of how much performance there is to be gained here. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers