Re: Lookup penalty for VARIADIC patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Lookup penalty for VARIADIC patch
Date: 2008-07-15 23:15:14
Message-ID: 14520.1216163714@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> writes:
> 2008/7/15 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> Also, it occurs to me that we could buy back a good part of the extra
>> space if we allowed pg_proc.probin to be NULL for internal functions.
>> Right now it's always "-" in that case, which is useless ...

> probin is used in some unofficial pl hacks, so this space its some
> times used.

Sure, if you want to use it you can. I'm just saying we should allow it
to be really NULL, instead of a dummy value, when it isn't being used.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Xiao Meng 2008-07-16 00:23:31 gsoc, store hash index tuple with hash code only
Previous Message Bruce Momjian 2008-07-15 22:56:31 Re: Core team statement on replication in PostgreSQL