Re: Issues for named/mixed function notation patch - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Issues for named/mixed function notation patch
Date
Msg-id 15840.1249843624@sss.pgh.pa.us
Whole thread Raw
In response to Issues for named/mixed function notation patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Issues for named/mixed function notation patch  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Oh, another thing: the present restriction that all function parameters
after the first one with a default must also have defaults is based on
limitations of positional call notation.  Does it make sense to relax
that restriction once we allow named call notation, and if so what
should we do exactly?  (This could be addressed in a followup patch,
it doesn't necessarily have to be dealt with immediately.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Issues for named/mixed function notation patch
Next
From: Robert Haas
Date:
Subject: Re: hot standby - merged up to CVS HEAD