Re: WIP: default values for function parameters

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
Cc: "Grzegorz Jaskiewicz" <gj(at)pointblue(dot)com(dot)pl>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>
Subject: Re: WIP: default values for function parameters
Date: 2008-12-09 15:23:49
Message-ID: 15180.1228836229@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/12/9 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> ... and it breaks an operator that's already in use.

> what is acceptable workaround? I unhappy, so this symbol was used for
> this minor contrib module (for this operator doesn't exists regress
> test).

If you could prove that it were *only* being used by this contrib module
then I might hold still for replacing it. But you can't. The odds are
good that people have custom data types using similarly-named operators.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2008-12-09 15:26:04 Re: contrib/pg_stat_statements 1202
Previous Message Magnus Hagander 2008-12-09 15:23:09 Re: new libpq SSL connection option