diff options
| author | Tom Lane | 2023-10-25 21:34:47 +0000 |
|---|---|---|
| committer | Tom Lane | 2023-10-25 21:34:47 +0000 |
| commit | 9e8a18d692a973a2bc1c19208bcb774fca8b90e8 (patch) | |
| tree | 4550c4e97d7713340ef6fe1bdb5f732cdd6c2122 /src | |
| parent | 93e1d5ce161508ad16deac3525b537355373a3e4 (diff) | |
Doc: remove misleading info about ecpg's CONNECT/DISCONNECT DEFAULT.
As far as I can see, ecpg has no notion of a "default" open
connection. You can do "CONNECT TO DEFAULT" but that just specifies
letting libpq use all its default connection parameters --- the
resulting connection is not special subsequently. In particular,
SET CONNECTION = DEFAULT and DISCONNECT DEFAULT simply act on a
connection named DEFAULT, if you've made one; they do not have
special lookup rules. But the documentation of these commands
makes it look like they do.
Simplest fix, I think, is just to remove the paras suggesting that
DEFAULT is special here.
Also, SET CONNECTION *does* have one special lookup rule, which
is that it recognizes CURRENT as an alias for the currently selected
connection. SET CONNECTION = CURRENT is a no-op, so it's pretty
useless, but nonetheless it does something different from selecting
a connection by name; so we'd better document it.
Per report from Sylvain Frandaz. Back-patch to all supported
versions.
Discussion: https://postgr.es/m/169824721149.1769274.1553568436817652238@wrigleys.postgresql.org
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions
