"NewbieDoc Docbook Guide" link broken

hi. in https://www.postgresql.org/docs/current/docguide-docbook.html the link (https://newbiedoc.sourceforge.net/metadoc/docbook-guide.html) for (NewbieDoc Docbook Guide) is broken. google around I found this [2] [2]: https://ftp.sun.ac.za/ftp/pub/documentation/newbiedoc/newbiedoc-html/docbook-g

Re: SEQUENCE keyword is option on GRANT

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 logged on the website: >> >> Page: https://www.postgresql.org/docs/17/sql-grant.html >> Description: >> >> The documentation

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

On Tue, Feb 18, 2025 at 7:06 AM David G. Johnston wrote: > > 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)

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

On Wed, Jan 22, 2025 at 12:53 AM Tom Lane wrote: > > jian he writes: > > https://www.postgresql.org/docs/current/functions-matching.html#FUNCTIONS-SIMILARTO-REGEXP > > > """ > > or as a plain three-argument function: > > substring(string, pattern,

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

hi. https://www.postgresql.org/docs/current/functions-matching.html#FUNCTIONS-SIMILARTO-REGEXP """ or as a plain three-argument function: substring(string, pattern, escape-character) """ but here "escape-character" is optional. substring(string, pattern [,escape-character]) would be more accura

Re: LC_COLLATE is visible in the documentation for PostgreSQL 17, but it is not supported

On Sat, Jan 4, 2025 at 11:53 PM PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/sql-show.html > Description: > > On the docs page for SHOW > (https://www.postgresql.org/docs/17/sql-show.html), LC_COLLA

restart-footnote-numbering-in-each-sect1

hi. https://www.postgresql.org/docs/current/tutorial-window.html#id-1.4.5.6.9.5 """ [5] There are options to define the window frame in other ways, but this tutorial does not cover them. See Section 4.2.8 for details. """ Why is "[5]"? I think generally we want to restart the footnote numbering in

Re: Document how to run only specific regress tests

hi. maybe verbose, the following is the my intended changes based on your patch. what do you think? Running Specific Tests You can run a subset of the regression tests through the TESTS environment variable. One way to do it is set TESTS environment variable beforehand: export T

Re: Tip box on Adding a Column

On Fri, Nov 1, 2024 at 5:06 PM Marcelo Fernandes wrote: > > Hi folks, > > We have this Tip box under the "Adding a Column" header here: > > - > https://www.postgresql.org/docs/current/ddl-alter.html#DDL-ALTER-ADDING-A-COLUMN > > That says: > > > From PostgreSQL 11, adding a column with a constant

Re: Document how to run only specific regress tests

On Tue, Oct 29, 2024 at 12:40 PM Paul A Jungwirth wrote: > > I never knew this was possible, but I ran across a note on the meson > wiki page[1]. I wish I knew about it years ago! > > This patch adds a note to > https://www.postgresql.org/docs/current/regress-run.html so that other > hackers and p

SET NAMES value value should be single quoted

NAMES SET NAMES value is an alias for SET client_encoding TO value. it should be: SET NAMES 'value' is an alias for SET client_encoding TO value. https://www.postgresql.org/docs/current/sql-set.html

Re: Undocumented := alternative in using option of raise statement

On Mon, Jul 22, 2024 at 8:38 PM PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/plpgsql-errors-and-messages.html > Description: > > The using option is documented as follows for all variants of the rai

Re: Add small detail to RAISE statement descripton

On Wed, May 22, 2024 at 11:35 PM Igor Gnatyuk wrote: > > Hi, > > thanks for the response and for your corrections to the patch. > But I checked my changes by running make html, make postgres-A4.pdf, > make postgres-US.pdf and viewing > the results: everything is OK. > > Message > 'old mode 100644

Re: Add small detail to RAISE statement descripton

mode 100644 new mode 100755 - i guess, that means your patch (fix_doc_raise_v3) has some structural problem. so I wrote it based on fix_doc_raise_v2.patch. please check attached. Feel free to change it. From 28f32f22095b262654ab204327678c7f027a5d36 Mon Sep 17 00:00:00 2001 From: jian he

Re: Add small detail to RAISE statement descripton

On Fri, May 17, 2024 at 4:39 PM Igor Gnatyuk wrote: > > Hi. > > Thank you for your letter. I tried to take your comments into account: > I added explanations to the condition_name, sqlstate options and > slightly changed > the explanations for USING. Attached you will find new patch version. > Tha

Re: Add small detail to RAISE statement descripton

On Tue, May 14, 2024 at 11:09 PM Igor Gnatyuk wrote: > > Hi, > > There is a slight syntax inaccuracy in the description of the RAISE > statement - assignments of parameter values in USING. > (Chapter 43. PL/pgSQL — SQL Procedural Language / 43.9 Errors and > Messages / 43.9.1 Reporting Errors and

Re: A typo?

On Sun, Apr 7, 2024 at 6:30 PM PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/plpgsql-declarations.html > Description: > > Under 43.3.1, "Notice that we omitted RETURNS real — we could have included >

Re: create table explicitly mention that unique|primary key constraint will create an

On Mon, Nov 27, 2023 at 10:30 AM Laurenz Albe wrote: > > What do you think of the attached patch? > > Yours, > Laurenz Albe looks good to me.

create table explicitly mention that unique|primary key constraint will create an

Hi. minor doc issue. create table s1(a int, constraint s2 PRIMARY key (a)); create table s2(a int); ERROR: relation "s2" already exists https://www.postgresql.org/docs/current/sql-createtable.html#SQL-CREATETABLE-PARMS-UNIQUE maybe for the following 2 sentence "Adding a unique constraint will aut

doc pg_describe_object description add a url link to pg_depend catalog.

Hi. made some changes in the pg_describe_object function description section. add a link to pg_depend. -pg_depend catalog. This function returns +pg_depend catalog. This function returns From 84c5ed57a270a5d916e89b747711a05daebd3dfa Mon Sep 17 00:00:00 2001 From: pgaddict Date: S

opclass. See below for details. cannot found the "below".

https://www.postgresql.org/docs/current/sql-createindex.html << opclass The name of an operator class. See below for details. << there is no "below"? Browser search, there are only four appearances of keyword "opclass". -- I recommend David Deutsch's <> Jian

Re: No explanation of other options

On Tue, Oct 17, 2023 at 7:00 PM PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/sql-move.html > Description: > > A few more examples with the other options would be helpful. > > MOVE LAST for example s

Re: Bug in documentation: https://www.postgresql.org/docs/current/spi-examples.html

On Tue, Jul 18, 2023 at 8:26 AM David G. Johnston wrote: > > No INFO messages appear because you did not include a returning clause. The > 1 you passed to the call is immaterial if the query you supply doesn't > produce a result set. > > David J. > indeed. https://www.postgresql.org/docs/curre

Re: Confusing reference to MERGE use inside WITH

On Sun, Jul 16, 2023 at 8:48 PM PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/queries-with.html > Description: > > Hi. > > In the queries WITH documentation > https://www.postgresql.org/docs/15/queri

9.7. Pattern Matching only a few links.

https://www.postgresql.org/docs/current/functions-matching.html 9.7. Pattern Matching is around 20 A4 pages, but there are only a few links. It would be better to have more links to some common functions like regexp_replace.

wiki postgresql Window_function some todo items is done?

Hi, https://wiki.postgresql.org/wiki/Todo#Window_Functions Implement full support for window framing clauses In addition to done clauses described in the latest doc > , > these clauses are not implemen

pg_relation_is_updatable, pg_column_is_updatable not documented

Hi, seems pg_column_is_updatable, pg_relation_is_updatable not documented. example: create view test_v_tenk1 AS select abs(unique1),unique1 from tenk1; select pg_catalog.pg_column_is_updatable('test_v_tenk1'::regclass, 2::smallint, false) select events & 4 != 0 AS upd, events & 8 != 0

https://wiki.postgresql.org/wiki/Meson add info about meson and ninja required version.

Hi, I'm trying to build with meson. --- rm -rf builddir meson setup \ --prefix=/usr/local/pg_master \ -Ddebug=true \ --bindir=/usr/local/pg_master \ --datadir=/usr/local/pg_master \ -Dpgport=1600 \ builddir cd builddir ninja ninja install

sql-select.html ordinal number of an output column.

quote from https://www.postgresql.org/docs/current/sql-select.html The elements of the PARTITION BY list are interpreted in much the same > fashion as elements of a GROUP BY > > clause, except that they are always simple express

Re: Does postgres have Equivalent range C range Ty​pe for Built-in SQL range Types

On Sun, Aug 28, 2022 at 4:07 PM Pavel Stehule wrote: > > > ne 28. 8. 2022 v 12:36 odesílatel Pavel Stehule > napsal: > >> Hi >> >> >> ne 28. 8. 2022 v 10:10 odesílatel jian he >> napsal: >> >>> >>> Equivalent C Types for B

Does postgres have Equivalent range C range Ty​pe for Built-in SQL range Types

Equivalent C Types for Built-in SQL Types https://www.postgresql.org/docs/15/xfunc-c.html#XFUNC-C-TYPE-TABLE Does postgres have Equivalent C range Type for Built-in SQL range Types? -- I recommend David Deutsch's <> Jian

Re: pg_stat_database view column xact_commit description should be more descriptive?

Sorry. It refers to all the transactions. On Fri, Jun 3, 2022 at 12:30 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > > > On Thursday, June 2, 2022, jian he wrote: > >> >> >> https://www.postgresql.org/docs/current/monitoring-stats.h

pg_stat_database view column xact_commit description should be more descriptive?

https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-DATABASE-VIEW > xact_commit bigint > > Number of transactions in this database that have been committed > In https://www.postgresql.org/docs/current/sql-begin.html BEGIN initiates a transaction block, that is, all st

Re: CREATE EXTENSION not adding extension on second SCHEMA

quote from manual: > CREATE EXTENSION loads a new extension into the current database. There > must not be an extension of the same name already loaded. > You can try to alter[1] the extension to make it located to another schema. [1]: https://www.postgresql.org/docs/14/sql-alterextension.html

collation.html natural sort

https://www.postgresql.org/docs/15/collation.html > Numeric ordering, sorts sequences of digits by their numeric value, for > example: A-21 < A-123 (also known as natural sort). > I guess maybe it should be 'A-21' < 'A-123' ? -- I recommend David Deutsch's <> Jian

43.10 Trigger Functions one sentences kind of not easy to understand.

https://www.postgresql.org/docs/current/plpgsql-trigger.html > > Row-level triggers fired BEFORE can return null to signal the trigger > manager to skip the rest of the operation for this row (i.e., subsequent > triggers are not fired, and the INSERT/UPDATE/DELETE does not occur for > this row). I

stxkind only explain two elements. left two unexplained.

PostgreSQL: Documentation: 10: 51.51. pg_statistic_ext > stxkind : An array containing codes for the enabled statistics kinds; > valid values are: d for n-distinct statistics, f for functional > dependency statistics select disti

list all the Boolean flags in pg_class that are maintained lazily.

PostgreSQL: Documentation: 14: 52.11. pg_class > Several of the Boolean flags in pg_class are maintained lazily: they are > guaranteed to be true if that's the correct state, but may not be reset to > false immediately when the condit

range data type size not mention in docs.

range type seem not mention their size in the docs. multi range size is variable. But range size seems fixed. why it's 17 byte? select pg_column_size('[10,20)' ::int4range ); --17 byte select pg_column_size('[-2147483648,2147483647)' ::int4range ); --17 byte.

Re: Data Type Size Calculation

https://www.depesz.com/2022/02/13/how-much-disk-space-you-can-save-by-using-int4-int-instead-of-int8-bigint/ Hope this link is useful. create table testb as select 'true'::bool as b from generate_series(1,100) i;SELECT 100 $ \dt+ testb List of relation