Re: Fixing row comparison semantics

Greetings to all,

On Mon, Dec 26, 2005 at 10:04:59AM -0500, Tom Lane wrote:
> I would recommend posting some fairly detailed design discussions
> concerning what you see as the new semantics, API, and catalog
> representation for operators and operator classes. If you haven't
> got buy-in at that level from the hackers list, it's premature to be
> writing any code at all.

Well, the problem works the other way around too. Unless you're
familiar with postgres internals you can't talk sensebly about the
changes required. Until two days ago I wasn't sure that my
representation was sufficient for everything I wanted it to do.

Anyway, the details posted before to -patches [1] and to -hackers [2]
produced much discussion about locales but didn't consider the actual
patch itself. I thought they were quite detailed and got exactly one
useful reaction: don't confuse collations and locales. Good advice and
the patch is better for it but I figured I needed to come up with
something more substantial for people to take notice.

Also, don't be confused about the time interval, there was zero
development on it from September until a few days ago, the changes
relative to then are not that large.

Now I can (almost) initdb again and have no more catalog changes I was
thinking of posting another patch with summary and see how far it gets
this time. BTW, my stuff won't change how ScanKeys work, they'll
probably just provide another way to initialise them.

Have a nice day,

[1] http://archives.postgresql.org/pgsql-patches/2005-09/msg00022.php
[2] http://archives.postgresql.org/pgsql-hackers/2005-09/msg00110.php

PS. The web archive for pg-patches seems to be lagging about 4 days
at the moment.
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.