Re: The document contains false statements

On Saturday, September 13, 2025, PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/sql-createfunction.html > Description: > > > This is effectively another way of declaring a name

Re: ANALYZE being a read v write operation clarification

On Friday, September 12, 2025, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/sql-analyze.html > Description: > > In the ANALYZE docs it states, > - "ANALYZE collects statistics about the contents of t

Re: CREATE TABLE LIKE(INCLUDING COMMENTS) description ignored STATISTICS

On Saturday, September 6, 2025, jian he wrote: > hi. > > https://www.postgresql.org/docs/devel/sql-createtable. > html#SQL-CREATETABLE-PARMS-LIKE-OPT-COMMENTS > """ > INCLUDING COMMENTS > Comments for the copied columns, constraints, and indexes will be copied. > The > default behavior is to excl

Re: SELECT List with/without parentheses

On Thursday, September 4, 2025, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/sql-select.html > Description: > > Here: https://www.postgresql.org/docs/current/sql-select.html > > There is no mention o

Re: Ambiguity in VALUES synopsis: LIMIT vs FETCH

On Tuesday, August 26, 2025, Cheng Ding wrote: > Hello docs team, > > I believe there’s an ambiguity in the VALUES command synopsis that can > mislead readers into thinking LIMIT and FETCH can be used together. > > *…* > > Alternatively, add a short note right under the synopsis: > > Note: FETCH

Re: Example on difference between CREATE MATERIALIZED VIEW and standard VIEW has typo

On Fri, Aug 22, 2025 at 2:23 PM PG Doc comments form wrote: > Unless I'm completely mistaken, the second code example on > https://www.postgresql.org/docs/current/rules-materializedviews.html, i.e > this: > > CREATE TABLE mymatview AS SELECT * FROM mytab; > > Should instead by > > CREATE VIEW mym

Re: Tutorial from Chapter 2.1

On Sunday, August 10, 2025, Tom Lane wrote: > > > Possibly we should reword the tutorial intro a bit, to the effect > that you can follow along with the examples if you have a source > tree at hand. (Sadly, that's not going to be very many novices > these days.) > I’d rather remove it from the d

Re: Tutorial from Chapter 2.1

On Sunday, August 10, 2025, PG Doc comments form wrote: > > Fix it so that access to the tutorial (since you have it) becomes > convenient > for ALL people with sources, binaries, installers, archives and any other > supplies. > Well, the main issue is the people who write the documentation and

Re: Lets prohibit predicting the future in the documentation.

On Monday, August 4, 2025, Álvaro Herrera wrote: > On 2025-Jul-31, David G. Johnston wrote: > > > > On Thu, Jul 31, 2025 at 8:05 PM Magnus Hagander > > > wrote: > > > > > I can agree that the "will likely be removed" is a bad wording, and > &g

Re: Lets prohibit predicting the future in the documentation.

On Thu, Jul 31, 2025 at 4:24 PM Peter Smith wrote: > On Thu, Jul 31, 2025 at 8:05 PM Magnus Hagander > wrote: > > > > > > > > On Thu, Jul 31, 2025 at 5:03 AM David Rowley > wrote: > >> > >> On Thu, 31 Jul 2025 at 14:17, David G. Johnston >

further clarification: alter table alter column set not null - table scan is skipped

On Thursday, July 31, 2025, Álvaro Herrera wrote: > On 2025-Jul-30, David G. Johnston wrote: > > > On Wed, Jul 30, 2025, 13:55 PG Doc comments form > > > wrote: > > > > The "table scan is skipped" optimization can use some clarification > > &g

Re: Lets prohibit predicting the future in the documentation.

On Wed, Jul 30, 2025 at 7:17 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > Came across this again today...we added, way back in v11: > > "This limitation will likely be removed in a future version of > PostgreSQL." > > Or, maybe phrase it: "Patches are welcomed." David J.

Lets prohibit predicting the future in the documentation.

Came across this again today...we added, way back in v11: "This limitation will likely be removed in a future version of PostgreSQL." https://www.postgresql.org/docs/18/sql-createstatistics.html David J.

Re: further clarification: alter table alter column set not null - table scan is skipped

On Wed, Jul 30, 2025, 13:55 PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/docguide.html > Description: > > Hello there, > I like PostgreSQL a lot so this is my way of giving back. > > The "table scan

Re: Clarification on the column order of UNION, INTERSECT, and EXCEPT

On Thu, Jul 24, 2025, 09:22 PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/queries-union.html > Description: > > When combining queries with UNION, INTERSECT, or EXCEPT, columns are > matched > in the

Re: Creating Database Querry in psql CLI

On Tuesday, July 15, 2025, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/tutorial-createdb.html > Description: > > The querry to create database you mentioned in this document (createdb > db_name) i

Re: please define 'statement' in the glossary

On Monday, July 14, 2025, Tom Lane wrote: > "David G. Johnston" writes: > > If we accept that we use the words statement and command interchangeably > > then the sole remaining use of command here sticks out because now we > have > > to explain why commands a

Re: please define 'statement' in the glossary

On Mon, Jul 14, 2025 at 10:09 AM Tom Lane wrote: > "David G. Johnston" writes: > > Ok. That explains why "statement_timestamp() and transaction_timestamp() > > return the same value during the first command of a transaction," isn't > > ju

Re: please define 'statement' in the glossary

On Mon, Jul 14, 2025 at 9:08 AM Tom Lane wrote: > "David G. Johnston" writes: > > Cannot readily test this presently but I wonder what the following > produces: > > > psql -c "begin; select statement_timestamp(), transaction_timestamp(); > > select st

Re: please define 'statement' in the glossary

On Mon, Jul 14, 2025 at 8:45 AM David G. Johnston < david.g.johns...@gmail.com> wrote: > I would then add an example In 53.2.2.1 showing this happening using "psql > -c" > > Cannot readily test this presently but I wonder what the following produces: psql -c "

Re: please define 'statement' in the glossary

On Mon, Jul 14, 2025 at 8:17 AM Tom Lane wrote: > Laurenz Albe writes: > > On Sun, 2025-07-13 at 17:32 -0700, David G. Johnston wrote: > >> We seldom if ever resort to including descriptions involving the fe/be > protocol > >> in the SQL portion of the documentat

Re: Add example to sort results by two composite types

On Sunday, July 13, 2025, PG Doc comments form wrote: > > I suggest to extend the example to sort results by first composite type and > then by the second: > SELECT * FROM invertory_type t, inventory_item c ORDER BY (c.name, > c.supplier_id, c.price), (t.name, t.value); > > Though I did not check

Re: Data visibility for returning statement

On Sat, Apr 26, 2025 at 5:50 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/dml-returning.html > Description: > > Today I found a pretty special use-case for the "RETURNING" functionality, > which I

Re: please define 'statement' in the glossary

On Sun, Jul 13, 2025 at 2:57 PM Tom Lane wrote: > ... so concretely, about like this? > > We seldom if ever resort to including descriptions involving the fe/be protocol in the SQL portion of the documentation - rightly considering (IMO) those to be implementation details (e.g., we don't even dir

Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html

On Sun, Jul 13, 2025 at 11:30 AM Tom Lane wrote: > I figured out how to make the 003_peer.pl tests for \1 less > hacky, and pushed that. Here's a proposed patch for the > documentation side of things, including your suggestion to > make pg_ident.conf.sample match up better. > > Thanks. My goal

Re: Unexpected behaviour: it was documented to return the same value

On Sunday, July 13, 2025, KES wrote: > I suppose that DEFAULT syntax should be used to set setting to its default > value. Eg. > set_config( 'my.option', DEFAULT, false ) > This is clear what should happen here. Also this syntax will correspond to > other places, eg. INSERT INTO xx (name) VALUES

Re: Outdated typedefs in documentation

On Wed, Jul 9, 2025 at 5:46 PM Artem Fadeev wrote: > I have noticed a slight mismatch between typedefs in docs and header > files. Your code is producing obvious false-positives by finding documentation examples and stating the obvious fact that such examples do not exist in the code base (sinc

Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html

On Wed, Jul 9, 2025 at 9:22 AM Tom Lane wrote: > "David G. Johnston" writes: > > On Wed, Jul 9, 2025 at 7:56 AM PG Doc comments form < > nore...@postgresql.org> > > wrote: > >> Pls. let me suggest the correction for the > >> https://www

Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html

On Wed, Jul 9, 2025 at 7:56 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/auth-username-maps.html > Description: > > Dear all, > Pls. let me suggest the correction for the > https://www.postgresql.

Re: Unexpected behaviour: it was documented to return the same value

On Mon, Jul 7, 2025 at 6:51 AM David G. Johnston wrote: > On Saturday, July 5, 2025, PG Doc comments form > wrote: > >> The following documentation comment has been logged on the website: >> >> Page: https://www.postgresql.org/docs/17/functions-admin.html >

Re: Unexpected behaviour: it was documented to return the same value

On Saturday, July 5, 2025, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/functions-admin.html > Description: > > set_config ( setting_name text, new_value text, is_local boolean ) → text > Sets the pa

Re: Cleanup of syntax.sgml

On Fri, Jun 20, 2025 at 2:21 PM Joshua Drake wrote: > > >> "We advise users who to read this chapter carefully ..." ? botched >> surgery on this one >> > > Not sure what you mean here? I reviewed the source sgml (that I modified): > > We advise users who to read this chapter carefully because it

Re: Cleanup of syntax.sgml

On Fri, Jun 20, 2025 at 12:33 PM Joshua Drake wrote: > To make it more consumable. > Overall I'm good with the attempt to trim, and most of the changes, but feel it tries to hard and ends up being to "matter-of-fact"; the conjunctions that exist make reading a wall of text easier. I agree that

Re: Clarify VACUUM FULL exclusion in total_vacuum_time docs

On Friday, June 6, 2025, Fujii Masao wrote: > Hi, > > Since last_vacuum and vacuum_count in pg_stat_all_tables explicitly mention > that they don't include VACUUM FULL ("not counting VACUUM FULL"), I think > we should add the same clarification to the description of > total_vacuum_time. > This fi

Re: PostgreSQL 17 default value assignment doesn't work in pgAdmin4 v9.4

On Sat, May 31, 2025 at 2:14 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > It's quite annoying that you didn't just copy the relevant SQL commands > and error messages into the email. Having to go through file share and > deal with images is quite annoyi

Re: PostgreSQL 17 default value assignment doesn't work in pgAdmin4 v9.4

On Sat, May 31, 2025 at 1:23 PM LUC PHEMBA wrote: > Can then someone explain me why the same format works in this case : > > *https://transfert.free.fr/P6wOY5x * > > but not in this other one : > > *https://transfert.free.fr/66abCAs

Re: Documentation should state what happens, when a commit fails

On Wed, May 28, 2025 at 7:47 AM mark maker wrote: > Wow, great improvement, thanks! > > The "tutorial-transactions" opens a new question that might be useful to > know: when a transaction enters the aborted state at an early point in time > (as has now become clear), does this mean it will also r

Re: Documentation should state what happens, when a commit fails

On Wednesday, May 28, 2025, Laurenz Albe wrote: > On Wed, 2025-05-28 at 08:08 +, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/17/sql-commit.html > > Description: > > > > Deferrable constraints

Re: Missing word

On Tuesday, May 13, 2025, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/ddl-partitioning.html > Description: > > In the paragraph: > https://www.postgresql.org/docs/current/ddl-partitioning. > html#DD

Re: Changes in CREATE EXTENSION from being an extension to statement

On Saturday, May 3, 2025, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/sql-createextension.html > Description: > > I wonder if it is appropriate to use "CREATE EXTENSION is a PostgreSQL > statement."

Re: 29.2. Subscription

On Wed, Apr 30, 2025 at 12:51 PM PG Doc comments form < nore...@postgresql.org> wrote: > > https://www.postgresql.org/docs/17/logical-replication-subscription.html#LOGICAL-REPLICATION-SUBSCRIPTION-EXAMPLES > > Have I misunderstood something, perhaps inadvertantly mis-configured some > obscure para

Re: Please clarify docs on user-defined settings for SET and RESET

On Monday, April 21, 2025, PG Doc comments form wrote: > > > It seems that the assumed/implied default value for settings that did not > exist for a session is the empty string? It would be useful to document > that > behavior explicitly. This is presently being worked on. Some changes have mad

Re: Suggestion for docs, section "4.2.3 Subscripts": bounds and base

On Thursday, April 3, 2025, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/sql-expressions.html > Description: > > I skimmed over section 4.2 while waiting for a meeting to start and found > no > menti

Re: generated constraint name

On Sunday, April 6, 2025, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/ddl-alter.html > Description: > > url: > https://www.postgresql.org/docs/current/ddl-alter.html# > DDL-ALTER-REMOVING-A-CONSTRAI

Re: Documentation for initdb option --waldir

he remote location is on a different physical device. An existing directory must be empty and should not be a mount point. The directory will be created (including missing parents) if necessary. David J. From be1ac8d7945668d5e31cb2c8aeabe879bfb9f86e Mon Sep 17 00:00:00 2001 From: "David G. J

Re: Ambiguity in IS JSON description and logic

On Thu, Mar 20, 2025 at 7:22 AM Kirk Parker wrote: > On Thu, Mar 20, 2025 at 7:08 AM Kirk Parker wrote: > >> >> On Thu, Mar 20, 2025 at 2:46 AM PG Doc comments form < >> nore...@postgresql.org> wrote: >> >>> The following documentation comment has been logged on the website: >>> >>> Page: https:

Re: SEQUENCE keyword is option on GRANT

On Mon, Mar 31, 2025 at 5:21 PM jian he wrote: > On Mon, Mar 31, 2025 at 9:55 PM David G. Johnston > wrote: > > > > > > On Monday, March 31, 2025, PG Doc comments form > wrote: > >> > >> The following documentation comment has been

Re: SEQUENCE keyword is option on GRANT

On Monday, March 31, 2025, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/sql-grant.html > Description: > > The documentation indicates that they keyword SEQUENCE must precede the > sequence_name in a

Re: Documentation for initdb option --waldir

On Saturday, March 29, 2025, Robert Treat wrote: > On Thu, Mar 27, 2025 at 5:57 PM David G. Johnston > wrote: > > On Thu, Mar 27, 2025 at 2:28 PM Robert Treat wrote: > >> On Thu, Mar 27, 2025 at 12:06 PM David G. Johnston > >> wrote: > >> > I

Re: Documentation for initdb option --waldir

On Saturday, March 29, 2025, Gurjeet Singh wrote: > On Sat Mar 29, 2025 at 9:26 AM PDT, Laurenz Albe wrote: > > > On the other hand, PostgreSQL will protest if the directory isn't > > empty... > > Specifically, initdb will complain if the directory it's trying to > initialize is not empty. > For

Re: Creating first database

On Friday, March 28, 2025, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/tutorial-createdb.html > Description: > > In the Getting Started section of the documentation which would be used by > a > new

Re: Documentation for initdb option --waldir

On Thu, Mar 27, 2025 at 2:28 PM Robert Treat wrote: > On Thu, Mar 27, 2025 at 12:06 PM David G. Johnston > wrote: > > > > Version 2 Attached > > > > -This option specifies the directory where the write-ahead log > > -should be stored. &g

Re: Documentation for initdb option --waldir

add a similar "why" to the mount point recommendation but don't know what that would be. Suggestions welcomed. David J. From 322acd64af51ae837af0d2e608b9e37aeb17baa8 Mon Sep 17 00:00:00 2001 From: "David G. Johnston" Date: Wed, 26 Mar 2025 17:12:57 -0700 Subject: [P

Re: Logical replication - initial data synchronization

On Sun, Dec 15, 2024 at 11:10 PM Peter Smith wrote: > On Mon, Nov 25, 2024 at 11:55 AM Peter Smith > wrote: > > > "When logical replication of a table starts, PostgreSQL typically > > takes a snapshot of the table's data on the publisher database and > > copies it to the subscriber." > > > > Thi

Re: substring synopsis section, third argument is optional doc didn't show that

On Tue, Jan 21, 2025 at 11:29 PM jian he wrote: > in 9.7.2 do you think it's worthwhile changing it to "" > As with SIMILAR TO, substring(string, pattern, escape-character) > the specified pattern must match the entire data string, or else the > function fails and returns null. > "" > ? > > Maki

Re: Improve examples: Provide the example which extend to the left of the range

On Tue, Jan 21, 2025 at 10:09 AM PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/functions-range.html > Description: > > It would be nice to have examples which `extend to the o

Re: Text correction

On Tue, Feb 11, 2025 at 2:16 PM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/textsearch-intro.html > Description: > > The page: https://www.postgresql.org/docs/17/textsearch-intro.html > The original

Re: Copy paste error

On Thu, Feb 13, 2025 at 7:44 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: > https://www.postgresql.org/docs/17/multivariate-statistics-examples.html > Description: > > CREATE STATISTICS stts (dependencies) ON a, b FROM t; > ANALYZE

Re: incorrect error message

On Wednesday, February 12, 2025, PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/sql-alterrole.html > Description: > > After changing to user postgres, I tried to launch psql sh

Re: creating a database

On Sunday, February 2, 2025, PG Doc comments form wrote: > > I guess this is on the server side, in a Linux shell or similar? > > I think this should be clarified in the text. We haven’t even mentioned psql yet, aside from the conventions page where we cover $ means a shell prompt. > And what

Re: Typo on tutorial window page

On Tue, Jan 21, 2025 at 10:39 AM Tom Lane wrote: > PG Doc comments form writes: > > EXPECTED: > > As shown here, the rank function produces a numerical rank for each > distinct > > PARTITION BY value in the current row's partition, using the order > defined > > by the ORDER BY clause. rank needs

Re: Typo on tutorial window page

On Tue, Jan 21, 2025 at 10:39 AM Tom Lane wrote: > PG Doc comments form writes: > > EXPECTED: > > As shown here, the rank function produces a numerical rank for each > distinct > > PARTITION BY value in the current row's partition, using the order > defined > > by the ORDER BY clause. rank needs

Re: docs are incomplete or wrong...

On Thursday, December 12, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/tutorial-createdb.html > Description: > > Folowing the online docs @ > https://www.postgresql.org/docs/17/tutorial-created

Re: Does NOTIFY leak information?

On Tuesday, December 3, 2024, PG Doc comments form wrote: > > I am interpreting this to mean that if I as user A receive a notification > to > a channel that I have set up, then user B and user C will also see this > notification, irrespective of their various permissions. Am I understanding > th

Re: Generated names (suffix) for constraints not described in docs

On Wednesday, November 13, 2024, "Сергей П (SergeiDos)" < podrezov.ser...@gmail.com> wrote: > > > > >

Re: Documentation error in tutorial page for Window Functions

On Sunday, November 10, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/tutorial-window.html > Description: > > In Section 3.5 Window Functions, the sentence that currently says: > "As shown here,

Re: https://www.postgresql.org/docs/current/sql-insert.html

On Saturday, November 2, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/sql-insert.html > Description: > > Is my suspicion valid? > The presence of the returning clause and subsequent usage of t

Re: Documentation mistake?

On Thursday, October 24, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/indexes-bitmap-scans.html > Description: > > In page https://www.postgresql.org/docs/current/indexes-bitmap-scans.html > на

Re: Undocumented optionality of handler_statements

On Wednesday, October 16, 2024, Bruce Momjian wrote: > On Wed, Sep 11, 2024 at 03:37:17PM +0900, Michael Paquier wrote: > > On Tue, Jul 23, 2024 at 01:25:39PM +0200, Philipp Salvisberg wrote: > > > read "optional" as "mandatory". > > > > They're optional, like in empty being optional. If not spe

A minor bug in doc. Hovering over heading shows # besides it.

On Wednesday, October 16, 2024, Bruce Momjian wrote: > > Where are we on this? I still see "#". > > We should document what we are doing in Conventions. The hover stuff is a nice usability add, if a bit limited on mobile. My +1 as well to matching Python with the pilcrow symbol. David J.

Re: Index of expression over table row or column

On Tuesday, October 15, 2024, Steve Lau wrote: > > I am reading this documentation[1], and it has a sentence that I don’t > quite understand: "The index columns (key values) can be either simple > columns of the underlying table or expressions over the table rows.”, I am > thinking that for the in

Re: [Issue] Getting started not oppening.

On Monday, September 23, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/tutorial-start.html > Description: > > This section in the documentation not opening. > > https://www.postgresql.org/docs/1

Re: The option was not described: connection-option

On Thu, Sep 19, 2024 at 10:31 AM Eugen Konkov wrote: > > I want to connect to 'postgres' database and dump 'mydb', because database > was turned to readonly mode and does not accept connections: > This is fundamentally impossible by the design of the system. You can only dump the database you c

Re: The option was not described: connection-option

On Thu, Sep 19, 2024 at 10:31 AM PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/app-pgdump.html > Description: > > Hi. > > The option `connection-option` is mentioned but is no

Re: Undocumented optionality of handler_statements

On Friday, September 13, 2024, Philipp Salvisberg < philipp.salvisb...@gmail.com> wrote: > >> Therefore, I suggest to change this example by adding a NULL > >> statement as in other examples. This change would make the > >> documentation consistent and handle the optionality of > >> handler_statem

Re: Mathematical Functions and Operators

On Saturday, September 7, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/functions-math.html > Description: > > Typically, exponentiation (which is represented here by ^) is a > right-associative

Re: retrieving results of procedures with OUT params

On Sat, Sep 7, 2024, 11:56 ch.l.ngre wrote: > > > > You are right, the documentation for CALL states that a row is being > returned. > However if you read > https://www.postgresql.org/docs/current/xproc.html#XPROC > 'Procedures do not return a function value; hence CREATE PROCEDURE lacks > a RETU

Re: retrieving results of procedures with OUT params

On Monday, September 2, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/libpq-exec.html > Description: > > https://www.postgresql.org/docs/16/libpq-exec.html#LIBPQ-PQRESULTSTATUS > Existing text:

Re: Behavior of ON DELETE CASCADE in CTEs

On Wednesday, September 4, 2024, Kirk Parker wrote: > > And the relevance to this current list is: if it IS intended behavior, can > it be documented somewhere? > It’s follows from this paragraph: https://www.postgresql.org/docs/current/queries-with.html#QUERIES-WITH-MODIFYING The sub-stateme

Re: suggestion about statement_timeout

On Saturday, August 31, 2024, yanliang lei wrote: > hi， > in the https://techcommunity.microsoft.com/t5/azure- > database-for-postgresql/connection-handling-best- > practice-with-postgresql/ba-p/790883 > there is the following description： > alter database dbnamehere set statement_timeout = 6000

Re: intarray extension installation

On Thursday, August 29, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/intarray.html > Description: > > Hi, > can you please specify somewhere that intarray extension is part of contrib > package

Re: Re: Supplements and suggestions and about postgresql sequence setval function in the documents

On Wed, Aug 21, 2024 at 4:41 PM yanliang lei wrote: > What I want to express is： >There is no description in the document that the schema name can be > included before the sequence name > > > Correct. It is here: All of the OID alias types for objects that are grouped by namespace accept sc

Re: Supplements and suggestions and about postgresql sequence setval function in the documents

On Wednesday, August 21, 2024, yanliang lei wrote: > > > in the following example; > select setval('seq_test',111); > ---this setval('seq_test',111) : update the current schema's seq_test > last_value =111 > > select setval('schemalei.seq_test',222); > ---this setval('seq_test',111) : update

Re: Documentation of .pgpass for Unix is incomplete

On Mon, Aug 19, 2024 at 5:06 PM Bruce Momjian wrote: > On Thu, Aug 8, 2024 at 09:44:51AM +, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/16/libpq-pgpass.html > > Description: > > > > The docu

Re: question about "vacuum full" command

On Friday, August 16, 2024, yanliang lei wrote: > > > I think the following is perfect in the document : adding the > description about vacumm full command （ not "vacuum full " > command） will influence which table. > Every command has a reference page in the docs where details like this are

Re: Tutorial clarify

On Wed, Aug 7, 2024 at 7:34 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/tutorial-install.html > Description: > > New and wanted to follow getting started docs but it seems it was written > for Un

Re: There is an invalid value for cidr type in the "Table 8.22. cidr Type Input Examples"

On Mon, Aug 5, 2024 at 4:30 PM Tom Lane wrote: > > On the whole I'm inclined to do nothing here; these docs have to > satisfy a number of requirements, and "every example should be > copy-and-pasteable" doesn't seem like a good constraint to add. > Another idea perhaps could be to remove enough d

Re: incorrect (incomplete) description for "alter domain"

On Mon, Jul 29, 2024 at 8:17 AM Tom Lane wrote: > I wrote: > > I think the page is technically correct, but I'm inclined to duplicate > > this text from the CREATE DOMAIN page: > > > where domain_constraint is: > > [ CONSTRAINT constraint_name ] > > { NOT NULL | NULL | CHECK (ex

Re: Typo in 15.3.4

On Mon, Jul 29, 2024 at 7:00 AM Daniel Gustafsson wrote: > On 25 Jul 2024, at 19:07, David G. Johnston > wrote: > > On Thu, Jul 25, 2024 at 9:50 AM PG Doc comments form < > nore...@postgresql.org> wrote: > >> The following documentation comment has been logged on

Re: incorrect (incomplete) description for "alter domain"

On Monday, July 29, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/sql-alterdomain.html > Description: > > In the Synopsis section of > https://www.postgresql.org/docs/current/sql-alterdomain.htm

Re: INSERT ... RETURNING documentation

On Thursday, July 25, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/sql-insert.html > Description: > > The grammar > [ RETURNING * | output_expression [ [ AS ] output_name ] [, ...] ] > seems wr

Re: Typo in 15.3.4

On Thu, Jul 25, 2024 at 9:50 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/parallel-plans.html > Description: > > In section 15.3.4, I believe "multiple results sets" is a typo for > "multiple > re

Re: wrong field in example

24, 2024 at 8:02 AM Yaroslav Saburov wrote: > >>because there is no single value for the column y that could be > associated with each group. > > 24 лип. 2024 р. о 17:51 David G. Johnston > пише: > >  > > > On Wed, Jul 24, 2024, 07:45 Yaroslav Saburov wrote: > >> group by y, not by x >> >> Why? > > David J. > >>

Re: wrong field in example

On Wednesday, July 24, 2024, David Rowley wrote: > On Thu, 25 Jul 2024, 12:57 am David G. Johnston, < > david.g.johns...@gmail.com> wrote: > >> I think you mis-copied the query - the one on the page has “select x”, >> not “select *”. >> > > That text exis

Re: wrong field in example

On Tuesday, July 23, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/queries-table-expressions.html > Description: > > >> In the second query, we could not have written SELECT * FROM test1 GROUP >

Re: A minor bug in the doc of "SQL Functions Returning Sets" in xfunc.sgml.

On Thu, Jul 18, 2024 at 9:05 PM Tom Lane wrote: > "David G. Johnston" writes: > > On Thu, Jul 18, 2024 at 7:10 PM Michael Paquier > wrote: > >> Not sure that this is worth changing. The examples work OK when taken > >> in isolation or are able to

Re: A minor bug in the doc of "SQL Functions Returning Sets" in xfunc.sgml.

On Thu, Jul 18, 2024 at 7:10 PM Michael Paquier wrote: > On Fri, Jul 19, 2024 at 10:46:04AM +0900, 日向充 wrote: > > I have found executable examples that do not work correctly > > in the doc of "SQL Functions Returning Sets" in xfunc.sgml. > > So I fixed the examples as follows. > > The attached pa

Re: A minor bug in doc. Hovering over heading shows # besides it.

On Wednesday, July 17, 2024, Tom Lane wrote: > David Rowley writes: > > On Thu, 18 Jul 2024 at 16:55, Muhammad Ikram wrote: > >> when we hover over Table Basics, it shows # sign postfixed. I think it > needs to be removed > > > In [1], there was some talk about using another more suitable > > c

Re: Column data type in doc example may be changed to VARCHAR from TEXT

On Wednesday, July 17, 2024, Muhammad Ikram wrote: > > > IMHO, a minor issue in the doc. As a good practice we use TEXT data type > when we expect longer text e.g. comments, doc kind of columns. > Who is we in this conversation? If it’s the documentation please reference existing work. Text is

Re: A minor bug in doc. Hovering over heading shows # besides it.

On Wednesday, July 17, 2024, Kashif Zeeshan wrote: > > > I have checked other pages too and the issue is only with this page. > There are like thousands of them… https://www.postgresql.org/docs/current/ddl-generated-columns.html#DDL-GENERATED-COLUMNS David J.

  1   2   3   4   5   6   >