Re: pgsql: Clarify dynamic pl/pgsql item and add URLs. - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.
Date
Msg-id 174.1150399185@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-committers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Tom Lane wrote:
>> The odds of that syntax getting accepted may not be exactly zero, but
>> they are certainly vanishingly small.  I thought we'd agreed that a
>> usable syntax would be like
>> get_employee_salary(12345 AS emp_id, 2001 AS tax_year)

> TODO updated, but I thought "=>" was the Oracle syntax.

So?  We don't support Oracle's brain-dead outer join syntax either.

            regards, tom lane

pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Use posix_fadvise() to avoid kernel caching of WAL contents on
Next
From: Bruce Momjian
Date:
Subject: Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.