I backed this out. It is part of a later patch still in the queue.
---
Bruce Momjian wrote:
>
> [ Sorry for previous message saying it was added to queue.]
>
> Patch applied. Thanks.
>
>
[ Sorry for previous message saying it was added to queue.]
Patch applied. Thanks.
---
Rod Taylor wrote:
> Appears there is a problem finding the opclass when indexing a domain.
>
> CREATE DOMAIN newint as int4;
> CREAT
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Rod Taylor wrote:
> Appears there is a problem
Thanks. I will keep it in the queue for CVS commit message sake.
---
Rod Taylor wrote:
> Sorry Bruce, this was included as a part of the patch of the below
> subject:
>
> Re: [PATCHES] Dump serials as serial -- not a sequ
Sorry Bruce, this was included as a part of the patch of the below
subject:
Re: [PATCHES] Dump serials as serial -- not a sequence
Patch may be smart enough to say 'already applied'.
On Wed, 2002-08-14 at 01:29, Bruce Momjian wrote:
>
> Your patch has been added to the PostgreSQL unapplied p
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Rod Taylor wrote:
> Appears there is a problem
Rod Taylor <[EMAIL PROTECTED]> writes:
> However, I have to wonder why GetDefaultOpClass doesn't simply use the
> first Binary Compatible opclass.
Because that would completely destroy the point of having multiple
opclasses for a datatype: you'd only do so if they *act different*.
Therefore, havi
Appears there is a problem finding the opclass when indexing a domain.
CREATE DOMAIN newint as int4;
CREATE TABLE tab (col newint unique);
ERROR: data type newint has no default operator class for access method
"btree"
You must specify an operator class for the index or define a