Re: docs are incomplete or wrong...

r response could be this: > createdb: error: connection to server on socket "/tmp/.s.PGSQL.5432" > failed: FATAL: role "joe" does not exist Specifically it says: > You will need to become the operating system user under which PostgreSQL > was installed (usually postgres) to create the first user account. Regards Ian Barwick

Re: Publishing Postgres Manual as a book

2023年3月23日(木) 12:34 Ian Lawrence Barwick : > > 2023年3月23日(木) 12:23 Erik Wienhold : > > > > > On 23/03/2023 02:35 CET Siddharth Jain wrote: > > > > > > The Postgres Manual is available online as a PDF but I think having it in > > > a > >

Re: Publishing Postgres Manual as a book

ributor could charge what they like. AFAIR the documentation has previously been published in book form, though as it runs to about 3,000 A4 pages now, the logistics are non-trivial. Regards Ian Barwick

Re: wiki postgresql Window_function some todo items is done?

aslo > The "latest doc" binded link > (developer.postgresql.org/pgdocs/postgres/sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS) > is not working. That URL structure is also pretty ancient; the current link is: https://www.postgresql.org/docs/devel/sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS Regards Ian Barwick

Re: Documentation: 21.5. Default Roles

les" should be thought of as "prefined roles", and note they will be called this from Pg13. Regards Ian Barwick -- Ian Barwick https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services

Re: doc: clarify "pg_signal_backend" default role

On 8/28/19 7:04 AM, Tom Lane wrote: Ian Barwick writes: Currently the documentation for the default role "pg_signal_backend" states, somewhat ambiguously, "Send signals to other backends (eg: cancel query, terminate)", giving the impression other signals (e.g. SIGHUP) ca

doc: clarify "pg_signal_backend" default role

ched patch clarifies this, adds a descriptive paragraph (similar to what the other default roles have) and a link to the "Server Signaling Functions" section. Patch applies cleanly to HEAD and REL_11_STABLE. Regards Ian Barwick -- Ian Barwick https://www.2ndQuadran

Re: Objects without schema

I suspect what this is trying to say is that you should keep all objects under one schema, and not explicitly reference that schema; that way queries and DDL would be more portable. Regards Ian Barwick -- Ian Barwick http://www.2ndQuadrant.com/ PostgreSQL Development, 24

Re: Request: Revive the security-specific section

Alvaro, That's exactly what I'd hope to see as well. On Sat, May 5, 2018, 12:45 PM Alvaro Herrera wrote: > Peter Eisentraut wrote: > > On 5/2/18 18:59, Ian Maddox wrote: > > > > It appears that the knowledge from that page has been redistributed > > >

Request: Revive the security-specific section

y be revived in a future revision of the manual. Thank you, Ian Maddox Google Cloud Solutions Architect

Re: Trigger behaviour not as stated

ements do not follow these update rules, so statements run on parent tables will insert rows in child tables if the trigger function so directs. The last line may need a bit of work, but I feel the text above it is clear. Ian On Mon, 29 Jan 2018 at 07:17 Bruce Momjian wrote: > On Sun, Jan

Trigger behaviour not as stated

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/static/sql-createtrigger.html Description: URL: https://www.postgresql.org/docs/current/static/sql-createtrigger.html Statement: "In contrast, row-level triggers are fired for all affecte