Docs for string_to_array missing for Postgres 14
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/14/functions-array.html Description: At the bottom of the docs on "Array Functions and Operators" for Postgres 14 (see https://www.postgresql.org/docs/14/functions-array.html) there is a NOTE with the text "There are two differences in the behavior of string_to_array from pre-9.1...". However I can't see that string_to_array function mentioned anywhere in the Postgres 14 docs, though it does appear in the Postgres 13 docs (see https://www.postgresql.org/docs/13/functions-array.html). I suspect the omission happened by accident because the function does exist in Postgres 14.1.
Re: No documentation exists about ecpg ORACLE comptaible mode
On Sat, Jul 09, 2022 at 09:15:52PM -0400, Bruce Momjian wrote: > This is a very good point. I have studied the issue and created the > attached patch to document Oracle-compatibility mode. > ... Looks good to me. Thanks a bunch Bruce. I wonder if we should also mention somewhere that some other Oracle compatibility features are enable in all modes, like a slightly different CONNECT syntax. Michael -- Michael Meskes Michael at Fam-Meskes dot De Michael at Meskes dot (De|Com|Net|Org) Meskes at (Debian|Postgresql) dot Org
Re: Docs for string_to_array missing for Postgres 14
PG Doc comments form writes: > At the bottom of the docs on "Array Functions and Operators" for Postgres 14 > (see https://www.postgresql.org/docs/14/functions-array.html) there is a > NOTE with the text "There are two differences in the behavior of > string_to_array from pre-9.1...". However I can't see that string_to_array > function mentioned anywhere in the Postgres 14 docs, We moved it to table 9.10 "Other String Functions": https://www.postgresql.org/docs/14/functions-string.html#FUNCTIONS-STRING-OTHER because it seemed to more naturally belong there. The NOTE you mention is gone altogether as of v15. regards, tom lane
Re: No documentation exists about ecpg ORACLE comptaible mode
On Tue, Jul 12, 2022 at 10:20:08AM +0200, Michael Meskes wrote:
> On Sat, Jul 09, 2022 at 09:15:52PM -0400, Bruce Momjian wrote:
> > This is a very good point. I have studied the issue and created the
> > attached patch to document Oracle-compatibility mode.
> > ...
>
> Looks good to me. Thanks a bunch Bruce.
Great, thanks.
> I wonder if we should also mention somewhere that some other Oracle
> compatibility features are enable in all modes, like a slightly different
> CONNECT syntax.
Good question. We support syntax from other databases, only sometimes
with documentation. I think the rules we use are that we document
compatibility-only behavior when it is useful and obviously if it is
turned in by an option.
In contrast, look at this from backend/parser/gram.y:
/* INOUT is SQL99 standard, IN OUT is for Oracle compatibility */
arg_class: IN_P{ $$ = FUNC_PARAM_IN; }
| OUT_P { $$ = FUNC_PARAM_OUT; }
| INOUT { $$ =
FUNC_PARAM_INOUT; }
| IN_P OUT_P{ $$ =
FUNC_PARAM_INOUT; }
| VARIADIC { $$ =
FUNC_PARAM_VARIADIC; }
We don't document "IN OUT" anywhere, we just support it silently for
Oracle compatibility, and I am guessing your ecpg connection syntax is
similar. I think this is done so we don't confuse people with syntax
that has not value unless they are coming from another database.
Therefore, I don't think we should document it, but I would be
interested to hear if anyone disagrees.
--
Bruce Momjian https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
64.4.2. Bottom-up Index Deletion
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/14/btree-implementation.html Description: on this url 64.4.2. Bottom-up Index Deletion, https://www.postgresql.org/docs/14/btree-implementation.html#BTREE-DELETION Would be nice to add a note: old tuple versions in the index referencing the same logical row cannot be deleted by bottom up index deletion process when older transactions that might require the old state the row are still running That is what the LP_DEAD bit is for I believe? hopefully my understanding is correct.
"Getting Started" guide is missing a critical step?
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/14/tutorial-createdb.html Description: Hello, I'm new to postgres so following through the steps in "Chapter 1. Getting Started". I was surprised to see that the chapter goes directly from "1.2 Architectural Fundamentals" to "1.3 Creating a Database" with no explanation of how to start a client application (ex: pgAdmin?) and how to connect to the local server. In other words, section 1.3 starts off with instructions for running the command "createdb mydb" but it's not clear where to run it. I think readers would benefit for an intermediate step between 1.2 and 1.3 that explains how to start the client software, how to connect to the server and where to run commands. Kind regards, Uri G.
Re: "Getting Started" guide is missing a critical step?
On Tuesday, July 12, 2022, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/tutorial-createdb.html > Description: > > Hello, > > I'm new to postgres so following through the steps in "Chapter 1. Getting > Started". > > I was surprised to see that the chapter goes directly from "1.2 > Architectural Fundamentals" to "1.3 Creating a Database" with no > explanation > of how to start a client application (ex: pgAdmin?) and how to connect to > the local server. In other words, section 1.3 starts off with instructions > for running the command "createdb mydb" but it's not clear where to run > it. > > I think readers would benefit for an intermediate step between 1.2 and 1.3 > that explains how to start the client software, how to connect to the > server > and where to run commands. > Per the conventions chapter it is made clear that thing command being run is an operating system executable in the shell, not an SQL command in some client program. The only client that will be considered is the command line psql client. The book as a whole assumes that you installation allows for connections to the postgres database to be done without any command line arguments or even a password, as trust or peer are assumed to work against the local socket. This is what “Getting Started - Installation” is rambling on about. The purpose here is just to setup a clean database to experiment in so the postgres database doesn’t get polluted. Hope that clears things up for you. David J.
