Re: Bug in pg_describe_object, patch v2 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Bug in pg_describe_object, patch v2
Date
Msg-id 28424.1295105808@sss.pgh.pa.us
Whole thread Raw
In response to Re: Bug in pg_describe_object, patch v2  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Bug in pg_describe_object, patch v2  (Joel Jacobson <joel@gluefinance.com>)
Re: Bug in pg_describe_object, patch v2  (Andreas Karlsson <andreas@proxel.se>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Jan 13, 2011 at 1:24 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Read the CREATE OPERATOR CLASS source code. �(It likely would be best to
>> refactor that a bit so it would expose some way to obtain the implied
>> defaults --- I don't think that's done explicitly now, and it's
>> certainly not exported from opclasscmds.c.)

> I didn't say I *couldn't* take the time to understand this; I said I
> think it'd be more clear to more people if we just printed the types
> all the time.

No, it would just be useless noise that would confuse most people,
especially since the default behavior varies across AMs.  Please observe
that not one single one of the contrib modules has any occasion to
specify non-default amprocleft/right --- that should give you a fix on
how useful it is to worry about what they are.  If it weren't for
binary-compatibility kluges we wouldn't need the ability to specify
these at all.

But I can read the handwriting on the wall: if I want this done right,
I'm going to have to do it myself.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Streaming base backups
Next
From: Florian Pflug
Date:
Subject: Re: kill -KILL: What happens?