Re: [PERFORM] Feature request: smarter use of
От
John Siracusa
Тема
Re: [PERFORM] Feature request: smarter use of
Дата
Msg-id
BC702779.30E6D%siracusa@mindspring.com
Ответ на
Список
Дерево обсуждения
Re: [PERFORM] Feature request: smarter use of conditional indexes John Siracusa <siracusa@mindspring.com>
Re: [PERFORM] Feature request: smarter use of conditional indexes Tom Lane <tgl@sss.pgh.pa.us>
Re: [PERFORM] Feature request: smarter use of John Siracusa <siracusa@mindspring.com>
Re: [PERFORM] Feature request: smarter use of Tom Lane <tgl@sss.pgh.pa.us>
Re: [PERFORM] Feature request: smarter use of conditional Neil Conway <neilc@samurai.com>
Re: [PERFORM] Feature request: smarter use of conditional Tom Lane <tgl@sss.pgh.pa.us>
Re: [PERFORM] Feature request: smarter use of John Siracusa <siracusa@mindspring.com>
Re: [PERFORM] Feature request: smarter use of Tom Lane <tgl@sss.pgh.pa.us>
On 3/7/04 12:48 AM, Tom Lane wrote: > John Siracusa 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
В списке pgsql-patches по дате отправления
От: Tom Lane
Дата: