Re: Mention the default io_method?

st 2. 4. 2025 v 12:28 odesílatel Daniel Westermann (DWE) mailto:daniel.westerm...@dbi-services.com>> napsal: Hi, https://www.postgresql.org/docs/devel/runtime-config-resource.html#GUC-IO-METHOD Shouldn't we mention that "worker" is the default? >+1 >Pavel ... atta

Mention the default io_method?

Hi, https://www.postgresql.org/docs/devel/runtime-config-resource.html#GUC-IO-METHOD Shouldn't we mention that "worker" is the default? Regards Daniel

Re: Ordering of statistic views

>> I am wondering if there is a reason that the list on top of: >> https://www.postgresql.org/docs/devel/monitoring-stats.html >> >> ... is not alphabetically ordered? >This was cleaned up most recently in commit 72e0ff2677c. Please check >there if the current arrangement does not match the guida

Ordering of statistic views

Hi, I am wondering if there is a reason that the list on top of: https://www.postgresql.org/docs/devel/monitoring-stats.html ... is not alphabetically ordered? Regards Daniel

Re: Incorrect mention of number of columns?

>"Daniel Westermann (DWE)" writes: >>> Yeah, but populating it would not (unless many of the columns were >>> NULL). >> Ok, but then should the documentation be more precise? It seems a bit odd to >> let users create such a table without at least a wa

Re: Incorrect mention of number of columns?

>"Daniel Westermann (DWE)" writes: >> Creating a table with 1600 bigint columns does work with a 8k blocksize: >Yeah, but populating it would not (unless many of the columns were >NULL). Ok, but then should the documentation be more precise? It seems a bit odd to let

Incorrect mention of number of columns?

Hi, from the limits page in the docs: https://www.postgresql.org/docs/current/limits.html "...but a tuple of 1600 bigint columns would consume 12800 bytes and would therefore not fit inside a heap page". Creating a table with 1600 bigint columns does work with a 8k blocksize: $ cat gen_tab.sh

Re: Missing word? https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-ARCHIVING-WAL

>>> "Another way to archive is to use a custom archive module as the >>> archive_library" >> >> shouldn't this read: >> "Another way to archive this is to use a custom archive module as the >> archive_library" >That would be worse than the original. What is "this"? >I'd suggest "Another way to

Missing word? https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-ARCHIVING-WAL

Hi, "Another way to archive is to use a custom archive module as the archive_library" shouldn't this read: "Another way to archive this is to use a custom archive module as the archive_library" Regards Daniel

Re: docs: set role permission checking, do I read this wrong?

On 10/18/23 09:26, David G. Johnston wrote: On Wednesday, October 18, 2023, Daniel Westermann wrote: "After |SET ROLE|, permissions checking for SQL commands is carried out as though the named role were the one that had logged in originally." Isn't it the o

docs: set role permission checking, do I read this wrong?

Hi, when reading the documentation about "set role" there is this: https://www.postgresql.org/docs/16/sql-set-role.html "After |SET ROLE|, permissions checking for SQL commands is carried out as though the named role were the one that had logged in originally." Given this: postgres=# select

Re: PostgreSQL 16 release notes: could cloud

Thanks, Bruce From: Bruce Momjian Sent: Monday, June 5, 2023 17:44 To: Daniel Westermann (DWE) Cc: pgsql-docs@lists.postgresql.org Subject: Re: PostgreSQL 16 release notes: could cloud On Mon, Jun 5, 2023 at 08:26:07AM +, Daniel Westermann (DWE) wrote

PostgreSQL 16 release notes: could cloud

Hi, E.1.3.1.4. Privileges # Simplify permissions for LOCK TABLE (Jeff Davis) Previously the ability to perform LOCK TABLE at various lock levels was bound to specific query-type permissions. For example, UPDATE could could perform all lock levels except ACCESS SHARE, which required SELECT perm

Do we really want to mention 8.3 in current versions of the docs?

Hi, do we really want to reference version 8.3 in current docs? https://www.postgresql.org/docs/current/row-estimation-examples.html -> "The outputs shown are taken from version 8.3" The examples seem to be more or less fine,. Regards Daniel

Re: Are we really using 23 bytes on most machines?

Thank you Send from my Mobile From: Simon Riggs Sent: Tuesday, September 20, 2022 3:48:02 PM To: Daniel Westermann (DWE) Cc: pgsql-docs@lists.postgresql.org Subject: Re: Are we really using 23 bytes on most machines? On Tue, 20 Sept 2022 at 13:24, Daniel

Are we really using 23 bytes on most machines?

Hi, https://www.postgresql.org/docs/current/storage-page-layout.html "(occupying 23 bytes on most machines)" Is this still true? At least on Linux it is 24 bytes: postgres=# select pg_column_size( row() ); pg_column_size   24 (1 row) Regards Daniel

Re: Can we still dump version 7?

>> >> Ugh, missed that, thanks for spotting it. >> I wonder whether we should update this or just remove it --- it's >> clearly something that's likely to get missed again. >While burdensome, +1 for updating. We don't want users to get caught by >surprise if pg_dumpall does not work on an old ve

Can we still dump version 7?

Hi, this commit (64f3524e2c8deebc02808aa5ebdfa17859473add) removed dump support for dumping from pre-8.0. I guess this statement is not true anymore? "Current releases of the dump programs can read data from any server version back to 7.0." https://www.postgresql.org/docs/current/upgrading.ht

Re: Should we really recommend "-A md5 or -A password"?

>> Yes I think we absolutely should! >+1 >Proposed patch attached. This also removes "-A password" from that >sentence as well. You've been faster than me :) Looks good. Regards Daniel

Should we really recommend "-A md5 or -A password"?

Hi, I just came across this: "Also, specify -A md5 or -A password so that the default trust authentication mode is not used;" https://www.postgresql.org/docs/current/creating-cluster.html Shouldn't we change that to "-A scram-sha-256" ? Regards Daniel

Re: Fir mkdir command in "Short Version" for installing from source

>> On 14 Mar 2022, at 15:01, Tom Lane wrote: >> >> Daniel Gustafsson writes: >>> On 13 Mar 2022, at 17:05, Daniel Westermann (DWE) >>> wrote: >>>> Is it worth fixing that with "mkdir -p ..."? >> >>> Well, it will fail

Fir mkdir command in "Short Version" for installing from source

Hi, if you follow that example step by step, the mkdir command will fail, obviously: https://www.postgresql.org/docs/current/install-short.html Is it worth fixing that with "mkdir -p ..."? Regards Daniel

Re: hot standby <-> Hot Standby

>"Daniel Westermann (DWE)" writes: >> which rules do we follow for writing hot standby? >The original author liked to capitalize it, but that's since been >followed only intermittently.  Personally I'd just as soon lose >the caps. Works for me, as long as it is consistent. Regards Daniel

hot standby <-> Hot Standby

Hi, which rules do we follow for writing hot standby? Looking here: https://www.postgresql.org/docs/current/hot-standby.html ... it does not seem to be consistent. We have "Hot Standby" and "hot standby" mixed throughout the page, e.g. "If a hot standby processes" "If the standby is not a hot s

Re: Be more clear what names can be used for tables with "CREATE TABLE"?

>>> "The name of the table must be distinct from the name of any other >>> relation (table, sequence, index, view, materialized view, or foreign >>> table) in the same schema." >> Works for me, +1 >Done that way, then. Thank you

Re: Be more clear what names can be used for tables with "CREATE TABLE"?

>Laurenz Albe writes: >> On Sat, 2021-10-30 at 11:08 +0000, Daniel Westermann (DWE) wrote: >>> in the documentation for CREATE TABLE we have this sentence: >>> "The name of the table must be distinct from the name of any other table, >>> sequence, index,

Re: Be more clear what names can be used for tables with "CREATE TABLE"?

>a) Don't forget: constraint, function, procedure, trigger. Functions don't count: postgres=# create function f() returns int as $$ select 1; $$ language sql; CREATE FUNCTION postgres=# create table f ( a int ); CREATE TABLE Procedures and constraints don't count: postgres=# create procedure p()

Be more clear what names can be used for tables with "CREATE TABLE"?

HI all, in the documentation for CREATE TABLE we have this sentence: "The name of the table must be distinct from the name of any other table, sequence, index, view, or foreign table in the same schema." At least materialized views are missing: postgres=# create materialized view t as select 1

Re: Wrong note in the information schema section?

  On Monday, August 30, 2021, David G. Johnston wrote: On Monday, August 30, 2021, Daniel Westermann (DWE) wrote: >>>Practically speaking there must be some level of scope where a duplicate >>>name error can occur.  All the docs say is that the schema >>>s

Re: Wrong note in the information schema section?

>>..."This is because the SQL standard requires constraint names to be unique >>within a schema, but PostgreSQL does not enforce this >>restriction." >>.. >>PostgreSQL does enforce unique constraint names in a schema: >>[...] >>... but I guess this is not what the notes is supposed to tell me, c

Wrong note in the information schema section?

Hi %. we have this note in the information schema section, e.g. in https://www.postgresql.org/docs/current/information-schema.html ..."This is because the SQL standard requires constraint names to be unique within a schema, but PostgreSQL does not enforce this restriction." ... PostgreSQL does

Re: Link missing in the 14 release notes

>On Thu, Jul  1, 2021 at 10:01:46PM -0400, Stephen Frost wrote: >> > Just a thought. >> > >> > Perhaps another idea would be to make one link which includes both >>names. >> >> Uh, that is going to look odd, I am afraid. >> >> This thread started with the point that the current en

Link missing in the 14 release notes

Hi, "Add predefined roles pg_read_all_data and pg_write_all_data (Stephen Frost) These non-login roles can be used to give read or write permission to all tables, views, and sequences." pg_read_all_data links to "Predefined roles", pg_write_all_data does not. Is that on purpose? At least it l

Link t the souce code

Hi, reading this: https://www.postgresql.org/docs/13/install-getsource.html ... I wonder if the link should not directly point to the relevant release, e.g.: https://www.postgresql.org/ftp/source/v13.2/ To me that seems to be more convenient than figuring that out on https://www.postgresql.org/d

Re: Functions should be Functions & Procedures

>On Wed, Nov 25, 2020 at 06:23:44PM +0000, Daniel Westermann (DWE) wrote: >> Hi Bruce, >> >> >On Tue, Nov 24, 2020 at 07:15:29PM +, PG Doc comments form wrote: >> >> The following documentation comment has been logged on the website: >> >>

Re: Functions should be Functions & Procedures

Hi Bruce, >On Tue, Nov 24, 2020 at 07:15:29PM +, PG Doc comments form wrote: >> The following documentation comment has been logged on the website: >> >> Page: https://www.postgresql.org/docs/13/plpgsql-overview.html >> Description: >> >> Hi, >> >> since PostgreSQL 11 we have procedures, so

Re: Wrong example in the bloom documentation

Hi, any thoughts on this? Regards Daniel From: Daniel Westermann (DWE) Sent: Sunday, September 27, 2020 17:58 To: Pg Docs Subject: Wrong example in the bloom documentation Hi, I've briefly discussed this with Bruce some time ago in [1]. Replayin

Wrong example in the bloom documentation

Hi, I've briefly discussed this with Bruce some time ago in [1]. Replaying the example referenced in the documentation does not give a Bitmap Heap Scan on tbloom but a parallel seq scan with the default configuration: -- tested on head postgres=# CREATE TABLE tbloom AS postgres-#SELECT postg

Relnotes for 13: There is word missing in UUID generation sentence

Hi, "Previously UUID generation functions were only available external modules uuid-ossp or pgcrypto were installed." Shouldn't that be: Previously UUID generation functions were only avai

Outdated tip in the "Adding a column section"

Hi, https://www.postgresql.org/docs/current/ddl-alter.html Tip Adding a column with a default requires updating each row of the table (to store the new column value). However, if no default is specified, PostgreSQL is able to avoid the physical update. So if you intend to fill the column with

Re: Supported versions missing at the top of the page

On Thu, Apr 4, 2019 at 10:24 AM Daniel Westermann (DWE) mailto:daniel.westerm...@dbi-services.com>> wrote: Hi, please check here: https://www.postgresql.org/docs/10/progress-reporting.html It only shows 9.6, 10 and 11 as "Supported Versions" on the top of the page. ==>

Supported versions missing at the top of the page

Hi, please check here: https://www.postgresql.org/docs/10/progress-reporting.html It only shows 9.6, 10 and 11 as "Supported Versions" on the top of the page. ==> Supported Versions: Current (11

66.3. Free Space Map

Hi %, while reading this [ https://www.postgresql.org/docs/10/static/storage-fsm.html | https://www.postgresql.org/docs/10/static/storage-fsm.html ] I am wondering if the first sentence should be adjusted. The free space map and the visibility are only there once vacuum touched the table, corr

Blanks in the first line before the first word in the code boxes

Hi, is it only me who sees blanks before the first word in the first line of the code boxes, e.g. here: [ https://www.postgresql.org/docs/9.6/static/sql-createtable.html | https://www.postgresql.org/docs/9.6/static/sql-createtable.html ] [ https://www.postgresql.org/docs/10/static/sql-create

Images in the official documentation

Hi %, I am working with PostgreSQL documentation quite a few years now and I am almost happy. What I think is completely missing (especially if you compare to commercial product documentation) are pictures that illustrate a topic, e.g. the relation of instance->database->user/role->schema->obj