| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org, cgg007(at)yahoo(dot)com |
| Subject: | Re: Schema search for default operator classes (was: [ADMIN] Cross schema Primary Key Indexes problem with datatype in the public schema) |
| Date: | 2006-02-09 12:42:48 |
| Message-ID: | 20060209124248.GC5234@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Tom Lane wrote:
> Given that we only allow one default opclass for a datatype regardless
> of schema (see DefineOpClass), it's not really necessary for
> GetDefaultOpClass to restrict its search. I can think of some corner
> cases involving multiple binary-compatible-datatype matches where the
> restriction might give a unique answer when an unrestricted search would
> not, but I kinda doubt this would ever arise in practice.
How about doing the constrained search first, and revert to the
unconstrained behavior if it doesn't find the desired opclass?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-02-09 14:09:45 | Re: Schema search for default operator classes (was: [ADMIN] Cross schema Primary Key Indexes problem with datatype in the public schema) |
| Previous Message | Martijn van Oosterhout | 2006-02-09 09:35:41 | Re: Schema search for default operator classes (was: [ADMIN] Cross schema Primary Key Indexes problem with datatype in the public schema) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | korry | 2006-02-09 12:51:11 | Re: pg_hba.conf alternative |
| Previous Message | Martijn van Oosterhout | 2006-02-09 12:38:06 | Re: User Defined Types in Java |