> First of all, volatility is not the only issue. The ordering ops could also
> be incorrect, e.g., violate the transitivity property. there is no reliable
> way to determine if a function is volatile and/or incorrectly specified.
No it is the only issue. If you create a datatype with volatile function for
ordering ops, then you have the broken data type(the one you are referring
to). So they are one and the same.
In response to
pgsql-hackers by date
|Next:||From: Gokulakannan Somasundaram||Date: 2010-02-26 04:24:08|
|Subject: Re: A thought on Index Organized Tables|
|Previous:||From: Pavan Deolasee||Date: 2010-02-26 04:19:47|
|Subject: Re: visibility maps and heap_prune|