Seeming contradiction in 22.1

On Thursday, March 23, 2023, maja zaloznik wrote: > > My point being that if what you say is true but runs counter to what > essentially all other instructions on the internet say, it would seem > prudent to mention this disparity and the reasons for it in the canonical > documentation, which

Re: Seeming contradiction in 22.1

On Wed, Mar 22, 2023 at 3:41 PM maja zaloznik wrote: > My issue is that - at least as far as i can recall - the default superuser > was already named postgres > There is no compiled-in default for the name of the bootstrap superuser. It is chosen during initdb using the algorithm described

Re: Seeming contradiction in 22.1

On Monday, March 20, 2023, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/database-roles.html > Description: > > In chapter 22.1 the following text seems to imply the role will have "the > same name

Re: Mistake in statement example

On Wed, Mar 1, 2023 at 9:34 AM Tom Lane wrote: > PG Doc comments form writes: > > I believe there is a mistake in an example on > > https://www.postgresql.org/docs/current/transaction-iso.html section > > 13.2.1: > > BEGIN; > > UPDATE accounts SET balance = balance + 100.00 WHERE acctnum =

Re: MERGE examples not clear

On Tue, Feb 21, 2023 at 8:35 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/sql-merge.html > Description: > > On this page: https://www.postgresql.org/docs/15/sql-merge.html > the first and second

Re: unclear syntax explanation for multiple window definitions in a SELECT query

On Thu, Feb 16, 2023 at 10:18 AM Adam Mackler wrote: > > Maybe the reference section for SELECT is the wrong place for that longer > form, but section 4.2.8 (or some other referenced from there) could be. > > Expanding Section 7.2.5 to be more consistent in level-of-detail with the rest of that

Re: unclear syntax explanation for multiple window definitions in a SELECT query

On Thu, Feb 16, 2023 at 5:13 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/sql-select.html > Description: > > The syntax documentation for SELECT in SQL COMMANDS section is unclear in > explaining

Re: Naming of network_ops vs. inet_ops for SP-GIST

Michael, please see below: On Tue, Jan 24, 2023 at 12:44 PM PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/spgist-builtin-opclasses.html > Description: > > I wanted to add an

Re: gen_random_uuid is only available with pgcrypto enabled

On Tue, Jan 24, 2023 at 12:43 PM PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/functions-uuid.html > Description: > > Regarding the documentation on this page: >

Re: https://www.postgresql.org/account/comments/new/15/sql-alterdatabase.html/

On Tue, Jan 24, 2023 at 12:43 PM PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/sql-alterdatabase.html > Description: > > Would love to see more information about each of the

Re: 8.5.2 "integral" - "integer"

On Saturday, January 7, 2023, Tom Lane wrote: > PG Doc comments form writes: > > I think, the "integer" will be good choice instead "integral'": > > 8.5.2 > > ... > > "The offset will be shown as hh (hours only) if it is an integral number > of > > hours, else as hh:mm if it is an integral

Re: 'value' has special behaviour in alter system

On Thu, Dec 15, 2022 at 4:45 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/sql-altersystem.html > Description: > > Documentation say > ALTER SYSTEM SET configuration_parameter { TO | = } { value |

Re: Clarify note about DISTINCT and ORDER BY in aggregates

On Thu, Dec 8, 2022 at 5:31 AM Vik Fearing wrote: > The current docs can be read as using DISTINCT in an aggregate > (count(distinct col)) and ORDER BY (array_agg(col ORDER BY col)) are > both extensions to the standard. > > The actual truth is that our extension to the standard is to allow both

Re: nextval parameter is not clear

On Sat, Dec 3, 2022 at 8:03 PM Kirk Wolak wrote: > On Thu, Dec 1, 2022 at 4:21 PM Laurenz Albe > wrote: > >> On Tue, 2022-11-29 at 16:26 -0500, Kirk Wolak wrote: >> > On Mon, Nov 28, 2022 at 12:45 AM Tom Lane wrote: >> > > Laurenz Albe writes: >> > > > Now I think that is taking it too far.

Re: Tutorial book with runable code for Postgres?

On Tue, Nov 29, 2022 at 2:42 PM Kirk Wolak wrote: > On Tue, Nov 29, 2022 at 3:40 AM Matous Jan Fialka wrote: > >> Hello. >> >> I would like to get some opinion on a petite idea I got while reading >> the "nextval >> parameter is not clear" thread. Because it may not fit well to the >> thread

Re: "jsonb ? text" operator and JSON strings

On Mon, Nov 28, 2022 at 1:34 PM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/functions-json.html > Description: > > The description of the "jsonb ? text" operator in table 9.45 specifies its >

Re: nextval parameter is not clear

On Mon, Nov 28, 2022 at 12:22 PM Kirk Wolak wrote: > On Mon, Nov 28, 2022 at 12:47 PM Tom Lane wrote: > >> Kirk Wolak writes: >> > my goal is to get an "approach" accepted, this is the first. >> Ultimately, I >> > would love to see >> > the documentation of functions with examples like this

Re: nextval parameter is not clear

On Fri, Nov 25, 2022 at 12:40 AM Laurenz Albe wrote: > On Thu, 2022-11-24 at 15:50 -0500, Kirk Wolak wrote: > > > > David, let me see how that looks. From an approach standpoint, I am > hearing: > > 1) Keep the example near the definition minimal [just this function] > > 2) It's okay to create

Re: nextval parameter is not clear

On Thu, Nov 24, 2022 at 7:33 AM Kirk Wolak wrote: > On Thu, Nov 24, 2022 at 5:33 AM Laurenz Albe > wrote: > >> On Thu, 2022-11-24 at 02:41 -0500, Kirk Wolak wrote: >> > Alright, as I have the documentation build working, and a slightly >> better stylesheet, >> > the comments on the last block

Re: nextval parameter is not clear

On Tue, Nov 22, 2022 at 8:42 PM Kirk Wolak wrote: > > > On Tue, Nov 22, 2022 at 2:10 PM Bruce Momjian wrote: > >> On Tue, Oct 18, 2022 at 08:17:12AM +, PG Doc comments form wrote: >> > The following documentation comment has been logged on the website: >> > >> > Page:

Re: Code example not following convention

On Sat, Nov 19, 2022 at 2:55 PM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/tutorial-window.html > Description: > > in: > https://www.postgresql.org/docs/current/tutorial-window.html > The example

Re: Merge statement

On Thu, Nov 17, 2022 at 12:48 PM Boboc Cristi wrote: > OK, I agree. I'll do my best to adopt the site conventions for every > specific type of site within the corresponding pages. > > *Top-posting is not by my choice, it is how the email client works.* > > Mine has the same default/convention.

Re: Merge statement

On Thu, Nov 17, 2022 at 12:06 PM Boboc Cristi wrote: > I agree that your statement is true, but it is still not quite self > sufficient. > > For the time being I have no idea how to make it easier to be understood. > As I have said, for me it is a little confusing. > > I would pay attention to

Re: Merge statement

On Thu, Nov 17, 2022 at 11:20 AM Boboc Cristi wrote: > Hello! > Thank you. I was fooled by the fact that sometimes it is marked with [...] > and other times with [,...] > > I think that consistency might worth attention, since [...] may indicate > "anything", while [,...] are more likely to

Re: 64.4.2. Bottom-up Index Deletion

On Wed, Nov 9, 2022 at 4:29 PM Peter Geoghegan wrote: > On Wed, Nov 9, 2022 at 2:20 PM David G. Johnston > wrote: > > Maybe a bit more explicitness is in order. > > Yeah, maybe. > > > On the point of "will generally need to coexist" - I don't see why we

Re: 64.4.2. Bottom-up Index Deletion

On Mon, Nov 7, 2022 at 5:20 PM Peter Geoghegan wrote: > Hi Hussein, > > Apologies for the very delayed response. I'm aware that you've taken > an interest in this subject as part of your YouTube channel. Thanks > for publicizing the work! > > On Tue, Jul 12, 2022 at 7:14 PM PG Doc comments form

Re: how to check specific user_name have “SELECT ON ALL TABLES IN SCHEMA ” privilege or not ?

On Sunday, September 11, 2022, yanliang lei wrote: > Dear everyone， > how to check specific have “SELECT ON ALL TABLES IN SCHEMA > ” privilege or not ? > This is not an appropriate list to ask general usage questions. We have a -general list for those. But, that isn’t a privilege. Its a

Re: No discussion of custom variables; no "See also" for set_config, current_setting, pg_settings

On Friday, September 2, 2022, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/sql-set.html > Description: > > A reader of this section > https://www.postgresql.org/docs/current/sql-set.html of the

Re: INSERT RETURNING

On Sun, Aug 28, 2022 at 7:51 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/dml-returning.html > Description: > > If I execute the below query > ``` > CREATE TABLE users ( > id serial primary

Re: documentation on HOT

On Sat, Jul 23, 2022 at 11:34 AM Peter Geoghegan wrote: > On Sat, Jul 23, 2022 at 8:51 AM Bruce Momjian wrote: > > Good points. I have updated the attached patch and URL to mention that > > HOT rows are _completely_ removed, and why that is possible, and I > > clarified the page item

Re: documentation on HOT

On Fri, Jul 22, 2022 at 8:09 AM Jonathan S. Katz wrote: > On 7/22/22 8:51 AM, Bruce Momjian wrote: > > On Thu, Jul 21, 2022 at 10:02:18PM -0400, Bruce Momjian wrote: > >> On Sun, Feb 6, 2022 at 09:29:56PM -0500, Jonathan Katz wrote: > >>> I agree with Bruce's point that we should have a new

Re: pg_advisory_unlock(null)

On Thu, Jul 14, 2022 at 6:36 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/functions-admin.html > Description: > > Hello! > There is no information in documentation about pg_advisory_unlock with

Re: CREATE TABLE AS, section IF NOT EXISTS should clarify what happens to the data

On Thu, Jul 14, 2022 at 6:08 PM Bruce Momjian wrote: > On Wed, Feb 9, 2022 at 01:02:51PM +, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/14/sql-createtableas.html > > Description: > > > > If

Re: Clarify the ordering guarantees in combining queries (or lack thereof)

On Thursday, July 14, 2022, Shay Rojansky wrote: > > If there's a guarantee that UNION ALL preserves ordering - as Tom seems to > indicate in the thread quoted above - then the above works. If there's no > such guarantee, then AFAIK the above can't be rewritten; putting the ORDER > BY outside -

Re: Clarify the ordering guarantees in combining queries (or lack thereof)

On Wed, Jul 13, 2022 at 5:08 PM Shay Rojansky wrote: > Greetings. > > I was trying to understand what - if any - are the guarantees with regards > to ordering for combining queries (UNION/UNION ALL/...). From this > message[1], it seems that UNION ALL does preserve the ordering of the > operand

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

Re: COPY FROM

On Fri, Jun 10, 2022 at 3:40 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/sql-copy.html > Description: > > When copying a csv file into a table, ifthere is a string missing a double > quote in

Re: correction

On Tue, Jun 7, 2022 at 5:26 PM Bruce Momjian wrote: > On Tue, Jun 7, 2022 at 08:00:16PM -0400, Tom Lane wrote: > > Bruce Momjian writes: > > > +not occur at certain isolation levels; > higher > > > > The docs toolchain is not gonna like that. > > You are correct. I should have tested,

Re: correction

On Tue, Jun 7, 2022 at 4:51 PM Bruce Momjian wrote: > On Tue, Jun 7, 2022 at 02:40:41PM -0700, David G. Johnston wrote: > > On Tue, Jun 7, 2022 at 2:07 PM Bruce Momjian wrote: > > > > > > > > How is this, attached? > > > > > > > >

Re: correction

On Tue, Jun 7, 2022 at 2:07 PM Bruce Momjian wrote: > > > How is this, attached? > > Works for me. Capital "S" in Standard as a proper name? (mind grepping this to see how consistent we are one way or the other, I'm not setup for that at the moment) David J.

Re: Mention RETURNING ... INTO target

n Tue, Jun 7, 2022 at 1:30 PM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/sql-insert.html > Description: > > It looks like INSERT INTO ... RETURNING allows defining a target for the > returned

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

On Thursday, June 2, 2022, jian he wrote: > > 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

Re: CREATE EXTENSION not adding extension on second SCHEMA

On Tuesday, May 31, 2022, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/sql-createextension.html > Description: > > I'm trying to add an extension to two schemas that I have in my DB. > > steps: > >

Re: correction

On Fri, May 13, 2022 at 2:49 PM Laurenz Albe wrote: > On Fri, 2022-05-13 at 16:36 -0400, Bruce Momjian wrote: > > On Wed, May 11, 2022 at 12:36:11PM +0200, Laurenz Albe wrote: > > > On Wed, 2022-05-11 at 00:33 +, PG Doc comments form wrote: > > > > The following documentation comment has

Re: SET TRANSACTION SNAPSHOT sounds like replicated environment but isn't

On Wed, May 11, 2022 at 7:33 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/sql-set-transaction.html > Description: > > Hello, > > the wording on the SET TRANSACTION SNAPSHOT left me a bit

Re: Docs about INSERT wait in Read Commited transaction

On Saturday, May 7, 2022, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/transaction-iso.html > Description: > > Hello > I've noticed, if two transactions in read committed mode are trying to > insert

Re: Specify bytes storage for enum data types

On Wednesday, May 4, 2022, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/datatype-enum.html > Description: > > I love Postgres !! And also its documentation !! > > While reading through data types,

Re: Clarification of triggers with 'OF column_name' in 'Overview of Trigger Behavior'

On Mon, May 2, 2022 at 6:55 PM David G. Johnston wrote: > On Mon, May 2, 2022 at 6:33 PM Josh Silver wrote: > >> >> and the 'Overview of Trigger Behavior pages says of before triggers >> >>> In row-level triggers the WHEN condition can examine the old

Re: Clarification of triggers with 'OF column_name' in 'Overview of Trigger Behavior'

On Mon, May 2, 2022 at 6:33 PM Josh Silver wrote: > > and the 'Overview of Trigger Behavior pages says of before triggers > >> In row-level triggers the WHEN condition can examine the old and/or new >> values of columns of the row. (Statement-level triggers can also have >> WHEN conditions,

Re: Clarification of triggers with 'OF column_name' in 'Overview of Trigger Behavior'

On Mon, May 2, 2022 at 4:42 PM Josh Silver wrote: > On Mon, May 2, 2022 at 3:22 PM David G. Johnston < > david.g.johns...@gmail.com> wrote: > >> On Mon, May 2, 2022 at 11:14 AM PG Doc comments form < >> nore...@postgresql.org> wrote: >> >>> The

Re: Clarification of triggers with 'OF column_name' in 'Overview of Trigger Behavior'

On Mon, May 2, 2022 at 11:14 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/13/trigger-datachanges.html > Description: > > UPDATE test SET alpha = 5; > > only trigger b2_ab will fire, even though it

Re: Documentation Suggestion

On Fri, Apr 29, 2022 at 7:07 AM Tom Lane wrote: > Alvaro Herrera writes: > > On 2022-Apr-28, David G. Johnston wrote: > > >> The page could use a hyperlink/cross-reference to the pg_hba.conf > >> documentation. > > > That's easily fixed. How about

Re: Documentation Suggestion

On Thu, Apr 28, 2022 at 12:36 PM PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/11/app-initdb.html > Description: > > Reference:

Re: 'CREATE OR REPLACE FUNCTION' behavior whenever a transaction is running

On Wed, Apr 20, 2022 at 12:50 PM PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/sql-createfunction.html > Description: > > The page does not mention what is the default

Re: What is a "simple expression"?

On Wed, Apr 20, 2022 at 12:50 PM PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/sql-select.html > Description: > > Hi there > > To start off I'd like to say your documentation

Re: incorrect information in documentation

On Mon, Aug 9, 2021 at 8:40 PM David G. Johnston wrote: > On Mon, Aug 9, 2021 at 11:05 AM Bruce Momjian wrote: > >> >> > selectivity = (1 - null_frac1) * (1 - null_frac2) * min(1/ >> > num_distinct1, >> > 1/num_distinct2) >

Re: Missing example for SAVEPOINT using the same savepoint name

ack to savepoint to note the behavior as well. commit e921441f22bad972393144628c7ee48845d5384c Author: David G. Johnston Date: Tue Apr 12 14:30:11 2022 + doc: Improve docs regarding savepoint name reuse Per documentation comment the savepoint command lacks an example where the sav

Re: Update wording of INSERT ON CONFLICT "rows proposed for insertion"

On Tue, Mar 8, 2022 at 5:14 PM David G. Johnston wrote: > > I suggest a minor rewording of: > > https://www.postgresql.org/docs/devel/sql-insert.html > > Concretely as attached. I did a bit more than minor work - I decided that actually calling it a table in the docs did

Re: 41.3. Materialized Views: Create table should be create view?

On Fri, Apr 8, 2022 at 2:06 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/rules-materializedviews.html > Description: > > CREATE TABLE mymatview AS SELECT * FROM mytab; > > Should be the creation

Re: stxkind only explain two elements. left two unexplained.

On Tuesday, April 5, 2022, Jian He wrote: > 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

Re: count() counts ROW values that are NULL

On Fri, Mar 18, 2022 at 3:06 PM Erwin Brandstetter wrote: > > On Fri, 18 Mar 2022 at 22:28, Tom Lane wrote: > >> Erwin Brandstetter writes: >> > >> https://www.postgresql.org/docs/current/functions-aggregate.html#FUNCTIONS-AGGREGATE-TABLE >> > The manual says: >> >> count ( "any" ) → bigint >>

Re: returning clause is not clearly documented

On Friday, March 11, 2022, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/dml-returning.html > Description: > > Hello there > I'm not good enough in english, so have my excuse. > > I don't undestand

Update wording of INSERT ON CONFLICT "rows proposed for insertion"

Hey, I suggest a minor rewording of: https://www.postgresql.org/docs/devel/sql-insert.html Current: "The SET and WHERE clauses in ON CONFLICT DO UPDATE have access to the existing row using the table's name (or an alias), and to [rows] proposed for insertion using the special excluded table."

Re: Missing information about CREATE TRIGGER on temporary tables

On Tue, Mar 8, 2022 at 9:25 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/sql-createtrigger.html > Description: > > To be confirmed by the developer community... > The reference page about CREATE

Re: SQL command : ALTER DATABASE OWNER TO

On Tue, Mar 8, 2022 at 7:39 AM Bruce Momjian wrote: > On Tue, Mar 8, 2022 at 10:50:38AM +0100, gp...@free.fr wrote: > > > > Hello, > > > > for this "ALTER DATABASE" form, it should be mentioned that after > execution of the command, > > the old database owner loses all his privileges on it

Re: Copy Documentation

On Thursday, February 17, 2022, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/sql-copy.html > Description: > > The documentation states that headers are only used for CSV files, but > there > is a

Re: range data type size not mention in docs.

On Wednesday, February 16, 2022, Jian He wrote: > > 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

Re: Does the POSITION() function takes into account the COLLATION... or not ?!?

On Tue, Feb 15, 2022 at 11:17 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/14/functions-string.html > Description: > > > SELECT POSITION(('å' COLLATE "en_US.utf8") IN

Re: Doc says nothing about wether CREATE OR REPLACE VIEW can change the COLLATION of an existing field

On Tue, Feb 15, 2022 at 8:04 AM PG Doc comments form wrote: > For this reason, I'm also filling a bug report, since postgresql's reaction > was not adapted to my request (neither an appropriate error message nor > successful execution of my SQL statement). > The bug report is valid and

Re: tutorial problem solution requires that problem is already fixed

On Tue, Feb 15, 2022 at 8:04 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/role-attributes.html > Description: > > I am reporting my roadblock, so it can be better documented in the future. > > I

Re: PL/pgSQL PERFORM WITH query

On Tue, Feb 8, 2022 at 3:14 PM Erwin Brandstetter wrote: > The manual currently reads: > > https://www.postgresql.org/docs/current/plpgsql-statements.html#PLPGSQL-STATEMENTS-GENERAL-SQL > > > PERFORM query; > > > This executes query and discards the result. Write the query the same > way you

Re: documentation on HOT

On Sun, Feb 6, 2022 at 6:08 PM Jonathan S. Katz wrote: > > Given the importance of HOT, it seems like this would be a good topic to > document. I would suggest something higher-level for general users in > the "Indexes"[4] section, and something lower-level in internals[5] > (which could perhaps

Re: Datetime formatting

On Thu, Jan 27, 2022 at 9:13 AM PG Doc comments form wrote: > > Page: https://www.postgresql.org/docs/14/datatype-datetime.html > > Might want to make a note that the current behavior does not match the > latest standard, but does match previous editions and/or RFC 3339. > We have such a note -

Re: Conventions

On Tuesday, January 25, 2022, Tom Lane wrote: > Bruce Momjian writes: > > How is this patch? > > I'd still drop the Tcl bit, or if you must have it, move it to > pltcl.sgml. Otherwise OK by me. > > > Agreed. David J.

Re: Conventions

On Tue, Jan 25, 2022 at 1:24 PM Bruce Momjian wrote: > On Tue, Jan 25, 2022 at 03:31:03AM +, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/12/notation.html > > Description: > > > > In section

Re: json_strip_nulls()

On Sat, Jan 22, 2022 at 12:11 PM Erwin Brandstetter wrote: > But the function also strips all insignificant white space: > > test=> SELECT json_strip_nulls(json '{"a": 1 , > test'> "foo" : "bar" > test'> }'); > json_strip_nulls >

Re: Not clear sentence

On Fri, Jan 21, 2022 at 5:37 AM Laurenz Albe wrote: > On Thu, 2022-01-20 at 19:46 +, PG Doc comments form wrote: > > Page: https://www.postgresql.org/docs/14/backup-dump.html > > Description: > > > > Text: This is necessary to fully backup the cluster if running the > pg_dump > > command on

Re: idle_session_timeout doc

On Wed, Jan 19, 2022 at 3:27 PM Capobianco, Tony wrote: > I have yet to find any instances where idle_session_timeout can be set at > the session level or applied to a single user. > > > https://www.postgresql.org/docs/current/sql-alterrole.html

Re: idle_session_timeout doc

On Wed, Jan 19, 2022 at 2:18 PM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/runtime-config-client.html > Description: > > Is there a way to alter users idle_session_timeout setting? My >

Re: Typo in "27.2.8. Synchronous Replication"

On Tue, Jan 18, 2022 at 4:01 PM Eric Mutta wrote: > > 2. I noticed the typo and on the top right of the page there's an "edit" > link. Click that and it takes you to GitHub where the Markdown text is. > I suspect a large part of your expectation is based upon this and that GitHub can display

Re: 11.7. Indexes on Expressions

On Wed, Dec 22, 2021 at 3:13 PM Bruce Momjian wrote: > I think our _big_ missing information is a definition of HOT updates and > that updating a column involved in an index disables HOT updates. > Along those lines adding "51.7 Special Considerations for Updates" would be minimally invasive.

Re: 11.7. Indexes on Expressions

On Wed, Dec 22, 2021 at 3:09 PM Bruce Momjian wrote: > On Wed, Dec 22, 2021 at 03:06:12PM -0700, David G. Johnston wrote: > > On Wed, Dec 22, 2021 at 2:45 PM Bruce Momjian wrote: > > Not sure what else we can do --- it would be odd to explain it in the > >

Re: 11.7. Indexes on Expressions

On Wed, Dec 22, 2021 at 2:45 PM Bruce Momjian wrote: > On Wed, Dec 22, 2021 at 02:40:12PM -0700, David G. Johnston wrote: > > On Fri, Dec 17, 2021 at 2:43 PM Bruce Momjian wrote: > > > > I am attaching an updated patch which mentions non-HOT updates for >

Re: 11.7. Indexes on Expressions

On Fri, Dec 17, 2021 at 2:43 PM Bruce Momjian wrote: > I am attaching an updated patch which mentions non-HOT updates for > expression indexes. > Thanks. I'm a bit concerned that before this patch the only place we mentioned HOTin the docs is in the appendix acronym listing which points to the

Re: Incorrect source directory in build instructions and build scripts

On Friday, December 10, 2021, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/14/install-windows-full.html > Description: > > I recently downloaded the source for PG 14 > >From where? > > assume the

Re: Array functions, array_length behavior given an empty array

On Monday, November 8, 2021, Pavel Stehule wrote: > Hi > > po 8. 11. 2021 v 13:48 odesílatel PG Doc comments form < > nore...@postgresql.org> napsal: > >> The following documentation comment has been logged on the website: >> >> I believe, such case deserves to be mentioned in the description

Re: text fields and performance for ETL

On Friday, November 5, 2021, Bruce Momjian wrote: > > > > > Perhaps, right before the tip you quoted, something like that: > > > > If your use case requires a length limit on character data, or > compliance > > with the SQL standard is important, use "character varying". > > Otherwise, you

Re: text fields and performance for ETL

On Thursday, November 4, 2021, Grega Jesih wrote: > > So why would it then be published ? Because inexperienced programmers take > your statement that "it's the same performance" from a wrong perspective, > so it would be fair to note, that the remark "it's the same performance" is > meant

Re: text fields and performance for ETL

On Wed, Nov 3, 2021 at 11:09 AM Grega Jesih wrote: > The new architectures include more and more data exchange among databases. > Now when you deal with bigger data sizes that go from millions to > billions, this fixed size vs of text - undefined size becomes very > relevant. > Can you

Re: text fields and performance for ETL

On Wed, Nov 3, 2021 at 8:35 AM Grega Jesih wrote: > Dear David, > > > The goal in our docs is to point out that using an arbitrary length > specification is not required in PostgreSQL. > > Then it should say so. Because unexperienced reader then uses this limited > focus and generalizes. > It

Re: text fields and performance for ETL

On Wed, Nov 3, 2021 at 6:55 AM PG Doc comments form wrote: > But performance in ETL processes related to such data type is decreased > dramatically, because any process that takes this kind of data needs to > calculate its size on a row level and cannot take bigger chunks of data > based on max

Re: [PATCH] doc/queries.sgml: add missing comma

On Tue, Oct 19, 2021 at 2:33 PM Tom Lane wrote: > Drew DeVault writes: > > Minor grammatical fix. > > Hmm, I'm not sure that reads any better than before. > > > > > -Strictly speaking, this process is iteration not recursion, but > > +Strictly speaking, this process is iteration,

Re: vacuumdb --analyze-in-stages

On Mon, Oct 18, 2021 at 4:02 PM Alvaro Herrera wrote: > On 2021-Oct-18, Euler Taveira wrote: > > > On Fri, Oct 8, 2021, at 6:33 AM, nikolai.berkoff wrote: > > > Running --analyze-in-stages on a database with statistics causes the > > > statistics to become significantly worse before they are

Re: Analyze on Foreign Data Wrappers - clarification

On Monday, October 11, 2021, PG Doc comments form wrote: > > Foreign tables are analyzed only when explicitly selected. > > 2. When I run the analyze command with the FDW table as a parameter > > That > Also, I am not clear if analyze is run on FDW tables when Automvacuum runs; > does it run

Re: Rolinherit- Role automatically inherits privileges of roles it is a member of

On Friday, October 1, 2021, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/view-pg-roles.html > Description: > > Roles do not inherit the rolconfig, please see the below labs, Yeah, just like the

Re: Common case not at all clear

On Sunday, September 19, 2021, Anthony Berglas wrote: > > I note that nothing has happened. > > In future I would suggest that you simply tell people that document > updates are not really welcome. Otherwise you waste people's time. > That isn’t generally true, and as I am not an Oracle my

Re: 13 25.1.1 clarify "The dumps produced by pg_dump are relative to template0"

On Thursday, September 16, 2021, PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/13/backup-dump.html > Description: > > Unless one knows > that template0 and template1 start off

Re: Keyword docs missing, or mislabelled keywords

On Thu, Sep 2, 2021 at 7:11 AM PG Doc comments form wrote: > > https://www.postgresql.org/docs/13/sql-keywords-appendix.html > > Missing: > > RESTRICTED (as found in CREATE FUNCTION (PARALLEL RESTRICTED)) > SAFE (as found in CREATE FUNCTION (PARALLEL SAFE)) > UNSAFE (as found in CREATE FUNCTION

Re: Simple re-wording

On Wednesday, September 1, 2021, PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/11/bug-reporting.html > Description: > > "Before you report a bug, please read and re-read the

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

<    1   2   3   4   >