On 2020-Sep-02, Tom Lane wrote:
> I don't think we should go overboard on this, but +1 for labeling all the
> cases where the usage isn't obvious.
+1
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Oleksandr Shulgin writes:
> On Wed, Sep 2, 2020 at 7:35 AM Andres Freund wrote:
>> In the docs we already name the parameters using SQL like syntax, see [1].
>> How about we actually do so for at least the more common / complicated
>> functions?
> I find myself in the same situation a lot.
> I'v
On 02/09/2020 19:15, Julien Rouhaud wrote:
On Wed, Sep 2, 2020 at 9:13 AM Oleksandr Shulgin
wrote:
On Wed, Sep 2, 2020 at 7:35 AM Andres Freund wrote:
Hi,
on a regular basis I remember a builtin function's name, or can figure it out
using \df etc, but can't remember the argument order. A typ
On Wed, Sep 2, 2020 at 9:13 AM Oleksandr Shulgin
wrote:
>
> On Wed, Sep 2, 2020 at 7:35 AM Andres Freund wrote:
>>
>> Hi,
>>
>> on a regular basis I remember a builtin function's name, or can figure it out
>> using \df etc, but can't remember the argument order. A typical example is
>> regexp_*,
On Wed, Sep 2, 2020 at 7:35 AM Andres Freund wrote:
> Hi,
>
> on a regular basis I remember a builtin function's name, or can figure it
> out
> using \df etc, but can't remember the argument order. A typical example is
> regexp_*, where I never remember whether the pattern or the input string
> c
Hi,
on a regular basis I remember a builtin function's name, or can figure it out
using \df etc, but can't remember the argument order. A typical example is
regexp_*, where I never remember whether the pattern or the input string comes
first.
Unfortunatly \df does not really help with that:
=# \
