Re: Discrepancy between the documentation and the implementation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: elkzwix(at)gmail(dot)com
Cc: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Discrepancy between the documentation and the implementation
Date: 2023-10-25 18:31:54
Message-ID: 1009483.1698258714@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

PG Doc comments form <noreply(at)postgresql(dot)org> writes:
> In the documentation for Postgres 15, on page
> https://www.postgresql.org/docs/15/ecpg-sql-set-connection.html, it states
> that one can write:

> SET CONNECTION connection_name

> And under that, it talks about "connection_name" and DEFAULT, which is
> supposed to be used in order to use the "default connection".
> However, "SET CONNECTION DEFAULT" is treated by ECPG as a normal connection
> name (looking for a connection named "DEFAULT"), not as a special keyword
> meaning to go back to using the "default" connection.

> Is there something I'm missing there ?

I don't see it either. Both that and EXEC SQL DISCONNECT claim
that DEFAULT is a specially treated name, but I don't see anything
in the underlying code that treats it differently. Perhaps there
was an intention to have some such feature but it never got done?

Anyway, I don't see anything indicating that there's actually
such a concept as "the default connection". I suggest we just
remove those paragraphs.

What *is* treated specially is CURRENT --- but EXEC SQL SET
CONNECTION = CURRENT is effectively a no-op, so it's not very
exciting.

regards, tom lane

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Maxim Yablokov 2023-10-26 07:33:50 Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table
Previous Message PG Doc comments form 2023-10-25 15:44:04 19.9. Secure TCP/IP Connections with SSL