Re: Copy paste error

Man... I looked at it 50 times before I posted that report. Sorry! Totally correct. Nothing to see here. On Thu, 13 Feb 2025 at 14:49, David G. Johnston wrote: > On Thu, Feb 13, 2025 at 7:44 AM PG Doc comments form < > nore...@postgresql.org> wrote: > >> The following documentation comment has

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

Copy paste error

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 t; EXPLAIN (ANALYZE, TIMING OFF) SELECT * FROM t WHERE a = 1 AND b = 1;

Re: incorrect error message

, I tried to launch psql shell as a new user > ( -U). However the error message I received after I used an incorrect > password was incorrect. It was saying that I had tried to wrong database. > Is > this correct? > > Yes, this is working as documented. If you don’t like which data

incorrect error message

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 shell as a new user ( -U). However the error message I received after I used an incorrect password

Re: Documentation error in tutorial page for Window Functions

Thanks, I see now. Then I'll suggest this clarification instead: "The rank function produces a numerical rank for each distinct value in the ORDER BY clause within the current row's partition. In this example, ranks are incremented in order of salary within each partition of depname. If the ORDER

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,

Documentation error in tutorial page for Window Functions

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, the rank function produces a numerical rank for each distinct ORDER BY

I use the example in this page ,but got error

: error: linker command failed with exit code 1 (use -v to see invocation)

Re: I get ERROR: column "table_name" does not exist

I made a gist with the error. https://gist.github.com/floratmin/a4b404f0fd66b03a0428c07686b71410 On Fri, Jun 7, 2024 at 3:24 AM Erik Wienhold wrote: > > On 2024-06-06 15:08 +0200, Florian Koch wrote: > > This is the working example, when I replace any of e.g. > > '

Re: I get ERROR: column "table_name" does not exist

On 2024-06-07 14:24 +0200, Florian Koch wrote: > I made a gist with the error. > https://gist.github.com/floratmin/a4b404f0fd66b03a0428c07686b71410 The problem is the semicolon after PG_DATATYPE_NAME, causing the TABLE_NAME line to be a separate statement: >exception

Re: I get ERROR: column "table_name" does not exist

> > When using GET STACKED DIAGNOSTICS in PL/pgSQL accessing TABLE_NAME, > > COLUMN_NAME, CONSTRAINT_NAME or SCHEMA_NAME throws an error. > > > > The function "shared.test_raise_exception": > > https://github.com/rin-nas/postgresql-patterns-library/issues/8#issuecomme

Re: I get ERROR: column "table_name" does not exist

; > > When using GET STACKED DIAGNOSTICS in PL/pgSQL accessing TABLE_NAME, > > > COLUMN_NAME, CONSTRAINT_NAME or SCHEMA_NAME throws an error. > > > > > > The function "shared.test_raise_exception": > > > https://github.com/rin-nas/postgresql-patt

Re: I get ERROR: column "table_name" does not exist

On 2024-06-04 21:50 +0200, PG Doc comments form wrote: > When using GET STACKED DIAGNOSTICS in PL/pgSQL accessing TABLE_NAME, > COLUMN_NAME, CONSTRAINT_NAME or SCHEMA_NAME throws an error. > > The function "shared.test_raise_exception": > https://github.com/rin-nas/po

I get ERROR: column "table_name" does not exist

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/plpgsql-control-structures.html Description: When using GET STACKED DIAGNOSTICS in PL/pgSQL accessing TABLE_NAME, COLUMN_NAME, CONSTRAINT_NAME or SCHEMA_NAME throws an error. The

Unclear which libpq functions set an error message for PQerrorMessage

age for PQerrorMessage if they fail. But which functions? I didn't find any further information in the documentation, except that for some functions it's explicitly documented that they set an error message. In particular, it doesn't seem to be documented which of the followi

Re: ERROR: plpython3u

> On 25 Jan 2024, at 05:58, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/tutorial-join.html > Description: > > CREATE EXTENSION plpython3u; > > [2024-01-25 05:5

ERROR: plpython3u

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/tutorial-join.html Description: CREATE EXTENSION plpython3u; [2024-01-25 05:56:50] [58P01] ERROR: could not load library "C:/Program Files/PostgreSQL/16/lib/plpython3.dll": The

Re: Error in Example

On 31/08/2023 01:29 CEST PG Doc comments form wrote: > Page: https://www.postgresql.org/docs/15/indexes-partial.html > Description: > > The IP addresses used to exemplify which one will be covered by the partial > index are inverted. No, the example is correct. It's about only indexing addresse

Error in Example

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/indexes-partial.html Description: The IP addresses used to exemplify which one will be covered by the partial index are inverted.

Re: ALTER TABLE "table" ALTER COLUMN "id" SET RESTART WITH nnn raises error

On Sun, Aug 20, 2023 at 8:56 AM PG Doc comments form wrote: > When the folloing SQL is executed: > ALTER TABLE "table" ALTER COLUMN "id" SET RESTART WITH nnn raises error > then an error is returned: > Yes, because if you take the RESTART branch in the synta

ALTER TABLE "table" ALTER COLUMN "id" SET RESTART WITH nnn raises error

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/sql-altertable.html Description: Hi, When the folloing SQL is executed: ALTER TABLE "table" ALTER COLUMN "id" SET RESTART WITH nnn raises error then an error

Re: doc build error on Fedora 38

Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= writes: > On Thu, 2023-04-06 at 20:18 +0800, Julien Rouhaud wrote: >> have >> you installed the required packages for that now that those files are >> available only via https, which isn't supported by any tool? > :-( Indeed, that is the problem. Apparently my s

Re: doc build error on Fedora 38

Hi Julien, On Thu, 2023-04-06 at 20:18 +0800, Julien Rouhaud wrote: > maybe you have a local copy of the docbook dtd on the older version? > have > you installed the required packages for that now that those files are > available only via https, which isn't supported by any tool? > https://www.pos

Re: doc build error on Fedora 38

On Thu, 6 Apr 2023, 19:11 Devrim Gündüz, wrote: > Hi, > > On Thu, 2023-04-06 at 13:10 +0200, Laurenz Albe wrote: > > Not sure if that helps, but could it simply be a problem accessing > > the network? > > Not sure. I can download and install all other tarballs, packages, etc. > maybe you have a

Re: doc build error on Fedora 38

Hi, On Thu, 2023-04-06 at 13:10 +0200, Laurenz Albe wrote: > Not sure if that helps, but could it simply be a problem accessing > the network? Not sure. I can download and install all other tarballs, packages, etc. Regards, -- Devrim Gündüz Open Source Solution Architect, PostgreSQL Major Contr

Re: doc build error on Fedora 38

following errors. Google did not help me that much. This > is libxml2-2.10.3 and libxslt 1.1.37 (same on Fedora 37). > > [...] > I/O error : Attempt to load network entity > http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd > [...] Not sure if that helps, but could it si

doc build error on Fedora 38

./src/backend/utils/errcodes.txt > errcodes-table.sgml '/usr/bin/perl' ./generate-keywords-table.pl . > keywords-table.sgml /usr/bin/xmllint --nonet --path . --path . --output postgres-full.xml -- noent --valid postgres.sgml I/O error : Attempt to load network entity http://www.oasis

Re: bytea documentation error

PG Doc comments form writes: > I believe there is a documentation error in the example for "8.4.1 bytea Hex > Format" > (https://www.postgresql.org/docs/current/datatype-binary.html#id-1.5.7.12.9). > The example is > `SELECT '\xDEADBEEF';` > However, wh

bytea documentation error

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/datatype-binary.html Description: I believe there is a documentation error in the example for "8.4.1 bytea Hex Format" (https://www.postgresql.org/docs/current/datatype-bina

Re: Not an error but a difficult wording

Laurenz Albe writes: > On Wed, 2023-01-25 at 20:39 -0500, Tom Lane wrote: >> I'd modify one word in your version: >> >>   These tools are not needed to build from a distribution tarball, because >>   the files generated using these tools are included in the tarball. >> >> Or possibly "with" inst

Re: Not an error but a difficult wording

On Wed, 2023-01-25 at 20:39 -0500, Tom Lane wrote: > Laurenz Albe writes: > > On Wed, 2023-01-25 at 08:22 +, PG Doc comments form wrote: > > > Maybe this would be better? (I don't know the comma rules) > > > "because the files(,?) that are generated/processed by these tools(,?) are > > > alrea

Re: Not an error but a difficult wording

Laurenz Albe writes: > On Wed, 2023-01-25 at 08:22 +, PG Doc comments form wrote: >> Maybe this would be better? (I don't know the comma rules) >> "because the files(,?) that are generated/processed by these tools(,?) are >> already included in the tarball" > +1 > Correct English would be:

Re: Not an error but a difficult wording

On Wed, 2023-01-25 at 08:22 +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/sourcerepo.html > Description: > > https://www.postgresql.org/docs/current/sourcerepo.html > > I was convinced that th

Not an error but a difficult wording

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/sourcerepo.html Description: https://www.postgresql.org/docs/current/sourcerepo.html I was convinced that there was a missing word or something in "because the files that these tools are

Re: error on „ 38.5. Query Language (SQL) Functions“: a single row is returned

PG Doc comments form writes: > The following documentation comment has been logged on the website: > Page: https://www.postgresql.org/docs/14/xfunc-sql.html > Description: > On the page „ 38.5. Query Language (SQL) Functions“ below the example > CREATE FUNCTION new_emp() RETURNS emp AS $$ >

error on „ 38.5. Query Language (SQL) Functions“: a single row is returned

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/14/xfunc-sql.html Description: On the page „ 38.5. Query Language (SQL) Functions“ below the example CREATE FUNCTION new_emp() RETURNS emp AS $$ SELECT ROW('None', 1000.0, 25, '(2,2)')::

Re: documentation error

> On 20 Aug 2022, at 12:39, PG Doc comments form wrote: > documentation says " The psql commands \df and \do can be used to list all > available functions and operators, respectively." > > which clearly indicates that those are built in function , please correct me > if I am wrong and I went to

documentation error

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/14/functions.html Description: Dear all, I am using documentation says " The psql commands \df and \do can be used to list all available functions and operators, respectively." which cle

Re: 34.16. The Password File error re windows pgpass.conf location

Hi, On Mon, Aug 08, 2022 at 05:45:38PM -0400, Tom Lane wrote: > PG Doc comments form writes: > > On this page: https://www.postgresql.org/docs/current/libpq-pgpass.html > > It incorrectly states: > > %APPDATA%\postgresql\pgpass.conf > > In reality this files needs to be placed here on a Windo

Re: 34.16. The Password File error re windows pgpass.conf location

PG Doc comments form writes: > On this page: https://www.postgresql.org/docs/current/libpq-pgpass.html > It incorrectly states: > %APPDATA%\postgresql\pgpass.conf > In reality this files needs to be placed here on a Windows system: > %APPDATA%\Roaming\postgresql\pgpass.conf >

34.16. The Password File error re windows pgpass.conf location

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/14/libpq-pgpass.html Description: On this page: https://www.postgresql.org/docs/current/libpq-pgpass.html It incorrectly states: %APPDATA%\postgresql\pgpass.conf In reality this files nee

Re: pgAdmin 4 (APT) installation error

Hi Robert, What does `lsb_release -cs` return in your system? If you are on bionic, it should return that. If it doesn't you have a broken lsb. El dom., 27 feb. 2022 22:41, robert escribió: > Hi, > > Great work. the page: >

pgAdmin 4 (APT) installation error

Hi, Great work. the page: https://www.pgadmin.org/download/pgadmin-4-apt/ has a series of commands one of which is to create a repository the line is: sudo sh -c 'echo "debhttps://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/$(lsb_release -cs) pgadmin4 main" > /etc/apt/sources.list.d/pgadmin4

Re: Minor error in calling a python list a tuple

e: > > > > Page: https://www.postgresql.org/docs/13/plpython-data.html > > Description: > > > > Hello, > > In the link bellow there is the mentioned error. > > https://www.postgresql.org/docs/13/plpython-data.html#PLPYTHON-ARRAYS > > > > CREATE FUN

Re: Minor error in calling a python list a tuple

On 01.02.22 20:57, PG Doc comments form wrote: The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/plpython-data.html Description: Hello, In the link bellow there is the mentioned error. https://www.postgresql.org/docs/13/plpython

Minor error in calling a python list a tuple

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/plpython-data.html Description: Hello, In the link bellow there is the mentioned error. https://www.postgresql.org/docs/13/plpython-data.html#PLPYTHON-ARRAYS CREATE FUNCTION make_pair

Re: Error in sample on doc page

-triggers.html Two issues here: 1) The CREATE EVENT TRIGGER command in the sample code does not execute (see output below) 2) When executed in an anonymous do block, there is no error. The CREATE EVENT TRIGGER executed outside the do block should have given an error saying already exists. Instead it gives

Re: Error in sample on doc page

On Mon, 2021-11-15 at 05:52 +, PG Doc comments form wrote: > Two issues here: > 1) The CREATE EVENT TRIGGER command in the sample code does not execute (see > output below) It works just fine for me. > 2) When executed in an anonymous do block, there is no error. The CREATE >

Error in sample on doc page

not execute (see output below) 2) When executed in an anonymous do block, there is no error. The CREATE EVENT TRIGGER executed outside the do block should have given an error saying already exists. Instead it gives the error: "ERROR: syntax error at end of input". ae_lake.cdc&g

Re: Error in sql script

On Tue, Aug 31, 2021 at 06:14:32PM -0700, David G. Johnston wrote: > On Tuesday, August 31, 2021, Mathieu Decelles St-Pierre < > mathieu.decelles.stpie...@gmail.com> wrote: > > So there is no SQL command that we can use to list the Text Search > Configurations on a system? > > > There is

Re: Error in sql script

So there is no SQL command that we can use to list the Text Search Configurations on a system? Mathieu mathieu.decelles.stpie...@gmail.com On Tue, Aug 31, 2021 at 3:22 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > On Tuesday, August 31, 2021, PG Doc comments form > wrote: > >> T

Re: Error in sql script

On Tuesday, August 31, 2021, Mathieu Decelles St-Pierre < mathieu.decelles.stpie...@gmail.com> wrote: > So there is no SQL command that we can use to list the Text Search > Configurations on a system? > There is…its not like psql has some special privilege to get that info from the server… You c

Re: Error in sql script

On Tuesday, August 31, 2021, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/13/textsearch-configuration.html > Description: > > In /13/textsearch-configuration.html, the last script block starts with > so

Error in sql script

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/textsearch-configuration.html Description: In /13/textsearch-configuration.html, the last script block starts with some incorrect characters and we do not see the sql command to list the T

Re: Logical error

On Wed, Jul 28, 2021 at 6:12 PM Bruce Momjian wrote: > On Fri, Jul 16, 2021 at 02:18:11PM -0500, Doug Tracy wrote: > > > > > > From the URL https://www.postgresql.org/files/documentation/pdf/12/ > > postgresql-12-A4.pdf > > > > Page xxxi > > > > PostgreSQL is an object-relational database managem

Re: Logical error

On Fri, Jul 16, 2021 at 02:18:11PM -0500, Doug Tracy wrote: >   > > From the URL https://www.postgresql.org/files/documentation/pdf/12/ > postgresql-12-A4.pdf > > Page xxxi > > PostgreSQL is an object-relational database management system (ORDBMS) based > on > POSTGRES, Version 4.21 > > Page 7

Logical error

>From the URL https://www.postgresql.org/files/documentation/pdf/12/postgresql-12-A4.pdf Page xxxi PostgreSQL is an object-relational database management system (ORDBMS) based on POSTGRES, Version 4.21 Page 7 2.2. Concepts PostgreSQL is a relational database management system (RDBMS)

Re: markdown error

> On 7 Jul 2021, at 09:17, PG Doc comments form wrote: > Tables for operators and functions in version 13 and devel 14 are broken These tables were deliberately changed to this format to allow for wide content. -- Daniel Gustafsson https://vmware.com/

markdown error

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/functions-json.html Description: Tables for operators and functions in version 13 and devel 14 are broken https://www.postgresql.org/docs/current/functions-json.html

Re: Error building for 64-bit Windows (10)

On Thu, May 27, 2021 at 07:21:16PM +0900, 近藤雄太 wrote: > First, the config option that specified the kerberos installation > directory was still "krb5", so we changed it to "gss". Thanks Kondo-san. Wow. So this has been actually untested for many years. The stuff got renamed in the MSVC scripts

Re: Error building for 64-bit Windows (10)

Hi, >>> @ Owners of hamerkop, could you look at updating the krb5 installation >>> on this animal? This include path used seems out of date compared to >>> the MSI installers upstream provides. >> >> OK. We'll have it done in a few days. > >Thanks! Thanks for your patience. We found some probl

Re: Error building for 64-bit Windows (10)

On Thu, May 20, 2021 at 11:04:05AM +0900, 近藤雄太 wrote: >> @ Owners of hamerkop, could you look at updating the krb5 installation >> on this animal? This include path used seems out of date compared to >> the MSI installers upstream provides. > > OK. We'll have it done in a few days. Thanks! -- Mi

Re: Error building for 64-bit Windows (10)

Hi Michael, > @ Owners of hamerkop, could you look at updating the krb5 installation > on this animal? This include path used seems out of date compared to > the MSI installers upstream provides. OK. We'll have it done in a few days. -- Kondo Yuta

Re: Error building for 64-bit Windows (10)

On Wed, May 19, 2021 at 10:56:23AM -0400, Andrew Dunstan wrote: > I have no idea - it's not my animal. Maybe ask the owner > Oops, I thought that this was yours. I am adding those folks in CC of this thread. > I guess maybe I should look at adding kerberos to one of the animals I > do control.

Re: Error building for 64-bit Windows (10)

On 5/18/21 8:15 PM, Michael Paquier wrote: > Hi Andrew, > > On Tue, May 18, 2021 at 08:15:35AM -0500, Brian Ye wrote: >> Thanks for the reply. >> Yes I also saw that after installing 64-bit, the 32-bit "bin" and "include" >> directories were removed. >> I think the content of the "include" are co

Re: Error building for 64-bit Windows (10)

Hi Andrew, On Tue, May 18, 2021 at 08:15:35AM -0500, Brian Ye wrote: > Thanks for the reply. > Yes I also saw that after installing 64-bit, the 32-bit "bin" and "include" > directories were removed. > I think the content of the "include" are common for both 32- and 64-bit. > Windows can run both 3

Re: Error building for 64-bit Windows (10)

Hi Michael, Thanks for the reply. Yes I also saw that after installing 64-bit, the 32-bit "bin" and "include" directories were removed. I think the content of the "include" are common for both 32- and 64-bit. Windows can run both 32-bit and 64-bit binaries so removing these 2 directories is probabl

Re: Error building for 64-bit Windows (10)

On Mon, May 17, 2021 at 08:07:02PM +, PG Doc comments form wrote: > The Solution.pm file has the following lines: > if ($self->{options}->{gss}) > { > $proj->AddIncludeDir($self->{options}->{gss} . '\inc\krb5'); > $proj->AddLibrary($self->{options}->{gss} . > '\

Error building for 64-bit Windows (10)

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/install-windows-full.html Description: The Solution.pm file has the following lines: if ($self->{options}->{gss}) { $proj->AddIncludeDir($self->{options}->{gss}

Re: BUG #16991: regclass is not case sensitive causing "relation does not exist" error

Thanks for the quick resolution. Best, Federico Ps: sorry for the previous messages in html, I had not realized that the client I was using were sending the replies like that. On Wed, 5 May 2021 at 17:28, Tom Lane wrote: > Laurenz Albe writes: > > On Tue, 2021-05-04 at 19:18 -0400, Tom Lane w

Re: BUG #16991: regclass is not case sensitive causing "relation does not exist" error

Laurenz Albe writes: > On Tue, 2021-05-04 at 19:18 -0400, Tom Lane wrote: >> So what I was remembering was some text in the section about sequence >> functions. That probably seemed appropriate when they were the only >> real use of regclass; but these days we have regclass-accepting functions >>

RE: BUG #16991: regclass is not case sensitive causing "relation does not exist" error

The patch is also clear for me, thanks for working on it. Best,Federico From: Laurenz AlbeSent: mercoledì 5 maggio 2021 09:32To: Tom Lane; FedericoCc: pgsql-docs@lists.postgresql.orgSubject: Re: BUG #16991: regclass is not case sensitive causing "relation does not exist" error On Tue,

Re: BUG #16991: regclass is not case sensitive causing "relation does not exist" error

On Tue, 2021-05-04 at 19:18 -0400, Tom Lane wrote: > [ redirecting to pgsql-docs list ] > > I wrote: > > Federico writes: > > > I did not come across that documented behavior while searching for > > > regclass > > > in the pg docs. The most relevant page I was able to find was the Object > > > I

Re: BUG #16991: regclass is not case sensitive causing "relation does not exist" error

[ redirecting to pgsql-docs list ] I wrote: > Federico writes: >> I did not come across that documented behavior while searching for regclass >> in the pg docs. The most relevant page I was able to find was the Object >> Identifier Types page that does not mention it. >> I'll look into proposing

Re: Possible Example Error in Documentation

hen I attempt > "CALL > >> transaction_test1();", I receive the "invalid transaction termination" > >> error. > > > > Hmm, it works for me. > > Ditto. > > I did get that error message if I put a "BEGIN;" statement before >

Re: Possible Example Error in Documentation

en I use the example given for >> transaction_test1() from the documentation here: >> https://www.postgresql.org/account/comments/new/12/plpgsql-transactions.html/, >> the procedure is created without incident. However, when I attempt "CALL >> transaction_test1();", I rece

Re: Possible Example Error in Documentation

umentation here: > https://www.postgresql.org/account/comments/new/12/plpgsql-transactions.html/, > the procedure is created without incident. However, when I attempt "CALL > transaction_test1();", I receive the "invalid transaction termination" > error. Hmm, it work

Possible Example Error in Documentation

/comments/new/12/plpgsql-transactions.html/, the procedure is created without incident. However, when I attempt "CALL transaction_test1();", I receive the "invalid transaction termination" error. Please correct the documentation if the example is flawed, or add an explanation on th

Re: 42.6.8.1. Obtaining Information About An Error

On Wed, Oct 7, 2020 at 12:57 PM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/plpgsql-control-structures.html > Description: > > 42.6.8.1. Obtaining Information About An Error >

42.6.8.1. Obtaining Information About An Error

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/plpgsql-control-structures.html Description: 42.6.8.1. Obtaining Information About An Error This example omits raise notice code: DECLARE text_var1 text; text_var2 text; text_var3

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

On Thu, Aug 27, 2020 at 09:12:39PM -0400, Tom Lane wrote: > I did not verify that the correct operators are listed, but visually > it looks OK. > > One thing I've noted in working with this stuff is that (at least for me) > HTML seems to default to valign=center while PDF defaults to valign=top. >

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

Alvaro Herrera writes: > On 2020-Aug-27, Michael Paquier wrote: >> This leads me to the updated version attached. BRIN has 29 different >> opclasses, visibly. > I checked both HTML and PDF and it looks good to me to commit. I did not verify that the correct operators are listed, but visually it

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

On 2020-Aug-27, Michael Paquier wrote: > This leads me to the updated version attached. BRIN has 29 different > opclasses, visibly. I checked both HTML and PDF and it looks good to me to commit. As a subsequent improvement we could discuss tweak the stylesheets to change the column widths in PD

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

On Wed, Aug 26, 2020 at 07:19:09PM -0400, Tom Lane wrote: > With one eye on the PDF width issue, I propose that we not draw > the distinction, but just list all the relevant operators for each > opclass (its native ones, plus the applicable "loose" operators). > Then we only need two columns, opcla

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

Alvaro Herrera writes: > On 2020-Aug-26, Bruce Momjian wrote: >> Stupid question, but do we think the average Postgres user can >> understand this issue. I am having trouble myself. > The only reason I think it's worth pointing out, is that the opclass > name is something you can use in CREATE I

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

s. And you can't use the opfamily name in CREATE INDEX: > > > > 55432 14devel 30811=# create index on t using brin (a integer_minmax_ops); > > ERROR: operator class "integer_minmax_ops" does not exist for access > > method "brin" > > > >

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

EX: > > 55432 14devel 30811=# create index on t using brin (a integer_minmax_ops); > ERROR: operator class "integer_minmax_ops" does not exist for access method > "brin" > > You have to use the opclass name: > > 55432 14devel 30811=# create index on t u

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

Alvaro Herrera writes: > On 2020-Aug-26, Michael Paquier wrote: >> I would imagine that rowsep=0 for a given can do that: >> https://tdg.docbook.org/tdg/4.5/entry.html >> However, it does not make a difference if I use the default style or >> the website style. I may be missing something with th

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

t one lists the operators for the opfamilies, not for the opclasses. And you can't use the opfamily name in CREATE INDEX: 55432 14devel 30811=# create index on t using brin (a integer_minmax_ops); ERROR: operator class "integer_minmax_ops" does not exist for access method "brin&

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

On Tue, Aug 25, 2020 at 06:17:28PM -0400, Tom Lane wrote: > Alvaro Herrera writes: >> (With the non-website stylesheet, as in the screenshot you showed, the >> table looks somewhat crammed and visually unappealing; but the website >> stylesheet looks pleasing enough. Screenshot attached.) Right,

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

Alvaro Herrera writes: > On 2020-Aug-25, Michael Paquier wrote: >> FWIW, the layout I was thinking about is something like the patch >> attached. > This looks to me enough of an improvement that I +1 it, and yes this is > what I was imagining also. I think it's a good idea too. > (With the non-

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

On 2020-Aug-25, Michael Paquier wrote: > I think so. If there are other places, it does not prevent improving > what we already know needs improvement. > > FWIW, the layout I was thinking about is something like the patch > attached. This looks to me enough of an improvement that I +1 it, and y

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

On Tue, Aug 25, 2020 at 01:44:03PM +0900, Michael Paquier wrote: > On Mon, Aug 24, 2020 at 12:01:00PM -0400, Bruce Momjian wrote: > > Sure, I can wait. Is this the only place where it would make sense? > > I think so. If there are other places, it does not prevent improving > what we already kno

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

On Mon, Aug 24, 2020 at 12:01:00PM -0400, Bruce Momjian wrote: > Sure, I can wait. Is this the only place where it would make sense? I think so. If there are other places, it does not prevent improving what we already know needs improvement. FWIW, the layout I was thinking about is something li

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

On Mon, Aug 24, 2020 at 11:59:22AM -0400, Alvaro Herrera wrote: > On 2020-Aug-24, Bruce Momjian wrote: > > > I don't think it is worth it, plus we would need to adjust the docs if > > system catalog layout changes. I think we just want something concise > > and simple, but also accurate. > > I a

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

On 2020-Aug-24, Bruce Momjian wrote: > I don't think it is worth it, plus we would need to adjust the docs if > system catalog layout changes. I think we just want something concise > and simple, but also accurate. I argued for \dAo, not straight catalog output -- that was a straw man. I can't

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

On Sat, Aug 22, 2020 at 02:59:02PM -0400, Alvaro Herrera wrote: > On 2020-Aug-22, Tom Lane wrote: > > > If you don't want to go all the way and list the operators with their > > input types, maybe we should just do what the OP thought was correct > > and delete the duplicate operator names. It's

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

On 2020-Aug-22, Tom Lane wrote: > If you don't want to go all the way and list the operators with their > input types, maybe we should just do what the OP thought was correct > and delete the duplicate operator names. It's already the case that > the table isn't telling you exactly which input ty

Re: Document "59.2. Built-in Operator Classes" have a clerical error?

Bruce Momjian writes: > Yeah, I kind of like the table myself too, because this topic is already > so complicated. Agreed. I'm not very happy with the suggestion of "(multiple)" though; I think that will just add confusion. If you don't want to go all the way and list the operators with their i

  1   2   >