Re: [PERFORM] Feature request: smarter use of

From: John Siracusa <siracusa(at)mindspring(dot)com>
To: Postgres Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [PERFORM] Feature request: smarter use of
Date: 2004-03-07 06:12:25
Message-ID: BC702779.30E6D%siracusa@mindspring.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On 3/7/04 12:48 AM, Tom Lane wrote:
> John Siracusa <siracusa(at)mindspring(dot)com> writes:
>> How does this look? It seems to do what I want without horribly
>> breaking anything as far as I can tell.
>
> Not a bad effort for a backend newbie ;-). It was lacking in comments,
> and upon inspection I thought it could be generalized a little.

I was trying to avoid catastrophe by confining myself to the exact case I
wanted to fix :) But even if I wasn't, I didn't understand the full meaning
of "strict" operators and functions. Actually, I'm still not sure how you
can conclude that foo is not null simply by seeing func(..., foo, ...) where
func() is strict. Do strict functions and operators simply not allow null
args?

Anyway, the world of typedefs and macros is definitely not my cup of tea.
Here's hoping that my next performance enhancement suggestion will be
complex enough that no one will entertain the thought of asking me for a
patch... ;)

-John

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-03-07 06:28:38 Re: [PERFORM] Feature request: smarter use of
Previous Message Tom Lane 2004-03-07 05:48:46 Re: [PERFORM] Feature request: smarter use of conditional indexes