Re: Monetary Data Types Improvement

On 3/20/24 11:07 AM, Dave Cramer wrote: On Wed, 20 Mar 2024 at 10:59, Erik Wienhold > wrote: On 2024-03-18 23:24 +0100, David Rowley wrote: > My vote would go to adding a deprecation notice to that section of the > docs.  There's some talk [1] about

Re: Include PostgresNIO Swift client in the Documentation

On 8/23/23 8:41 AM, Daniel Gustafsson wrote: On 22 Aug 2023, at 16:25, Jonathan S. Katz wrote: On 8/22/23 3:10 AM, Daniel Gustafsson wrote: This is in line with what I imagined as well, so unless anyone thinks otherwise I will apply this and backpatch it to all branches. I could argue

Re: Include PostgresNIO Swift client in the Documentation

On 8/22/23 3:10 AM, Daniel Gustafsson wrote: This is in line with what I imagined as well, so unless anyone thinks otherwise I will apply this and backpatch it to all branches. I could argue it both ways on whether or not to backpatch. However, given the list of drivers should work with all

Re: Include rust as an externally maintained procedural language

On 8/22/23 3:24 AM, Daniel Gustafsson wrote: On 22 Aug 2023, at 05:35, Jonathan S. Katz wrote: On 8/12/23 12:45 PM, Bruce Momjian wrote: On Fri, Aug 11, 2023 at 05:05:48PM -0400, Jonathan Katz wrote: On 8/11/23 2:46 PM, PG Doc comments form wrote: Considering the increasing support

Re: Include rust as an externally maintained procedural language

On 8/12/23 12:45 PM, Bruce Momjian wrote: On Fri, Aug 11, 2023 at 05:05:48PM -0400, Jonathan Katz wrote: On 8/11/23 2:46 PM, PG Doc comments form wrote: Considering the increasing support and stability for PL/Rust, it should be referenced within Postgresql's docs [1]. There's an up-to-date

Re: Include PostgresNIO Swift client in the Documentation

On 8/21/23 10:55 AM, Jonathan S. Katz wrote: On 8/21/23 7:58 AM, Daniel Gustafsson wrote: On 11 Aug 2023, at 02:23, Jonathan S. Katz wrote: The last time this came up, I think we discussed linking to the wiki page from the docs, vs. trying to keep the docs up-to-date with all

Re: Include PostgresNIO Swift client in the Documentation

On 8/21/23 7:58 AM, Daniel Gustafsson wrote: On 11 Aug 2023, at 02:23, Jonathan S. Katz wrote: The last time this came up, I think we discussed linking to the wiki page from the docs, vs. trying to keep the docs up-to-date with all of the drivers available. Perhaps it's worth seeing if we

Re: ROWS vs RANGE in release notes for pg 16

Hi Erwin, On 8/18/23 7:41 PM, Erwin Brandstetter wrote: The release notes for Postgres 16 says here: https://www.postgresql.org/docs/16/release-16.html#RELEASE-16-PERFORMANCE > Allow window functions to use ROWS mode

Re: Include rust as an externally maintained procedural language

On 8/11/23 2:46 PM, PG Doc comments form wrote: The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/external-pl.html Description: The documentation [1] contains a list of independently maintained procedural languages. Recently, PL/Rust

Re: Include PostgresNIO Swift client in the Documentation

Hi Fabian, On 8/10/23 3:55 AM, PG Doc comments form wrote: The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/external-interfaces.html Description: Hi, I'm reaching out to ask if the Swift Postgres could be included in the listing

Re: Clarify errhint in sources.sgml

On 7/12/23 3:08 AM, Daniel Gustafsson wrote: It was noted in 20230712015948.byqaftt57glwk...@awork3.anarazel.de that the errhint example in sources.sgml isn't as helpful as it could be. errhint should use a complete sentence, but the example doesn't, so I propose the attached change which makes

Re: Change "two" to "three" for decades of development in history

On 6/22/23 9:23 PM, Tom Lane wrote: Michael Paquier writes: "With multiple decades of development behind it, PostgreSQL.." +1. It sure seems silly trying to automate changing this. +1. With the proposed language, we can revisit it once it gets to "centuries." Jonathan

Re: large scale reliable software system

On 6/21/23 12:52 PM, B M wrote: Dear all, After greeting, I taught PostgreSQL myself and developed a small scale experimentalsoftware system using PostgreSQL in the back-end. I would like to know your advices to develop a large scale reliable software system using PostgreSQL in the

Re: confusing positioning of notes in connection settings

On 6/7/23 11:17 AM, Peter Eisentraut wrote: The proposed text in the patch is "This parameter is supported only on systems that {have this property} (which does not include Windows)." I don't see how the change you are proposing is correct. I see -- I had read it quickly and didn't sound

clarifying trigger/rule behavior on logical replication subscribers

in the "architecture" section. Thanks, Jonathan [1] https://www.postgresql.org/docs/devel/logical-replication-architecture.html From 23aaa7fe401d85736ebf426626b063075a75c918 Mon Sep 17 00:00:00 2001 From: "Jonathan S. Katz" Date: Tue, 6 Jun 2023 09:51:32 -0400 Subject: [PATCH] do

Re: confusing positioning of notes in connection settings

On 5/31/23 7:53 AM, Daniel Gustafsson wrote: On 31 May 2023, at 13:16, Peter Eisentraut wrote: The first two hunks are pretty straightforward, they just move the existing text around. For the other two, which are not supported on Windows, I added an explicit parenthetical note. We don't

Re: The use "Postgres" in docs

On 3/14/23 7:31 AM, Alvaro Herrera wrote: On 2023-Mar-14, Daniel Gustafsson wrote: The docs use PostgreSQL and not Postgres in all but two places, which I think we should change like in the attached to be consistent. Any objections to this? Both are very new. No objection to the change.

Re: February 9th, 2023 Release links to a missing page

On 2/20/23 8:57 PM, Kirk Wolak wrote: On Sun, Feb 19, 2023 at 4:55 PM Jonathan S. Katz Well, that gives me an idea. In the release announcement, we could put a line that says "You can send any corrections or suggestions to the public pgsql-...@lists.postgresq

Re: February 9th, 2023 Release links to a missing page

On 2/19/23 3:55 PM, Kirk Wolak wrote: On Wed, Feb 15, 2023 at 2:05 PM Jonathan S. Katz <mailto:jk...@postgresql.org>> wrote: The release announcements go through the news system, which does not have a feedback collection mechanism as anyone can post news. Emailing p

Re: February 9th, 2023 Release links to a missing page

On 2/15/23 1:59 PM, Kirk Wolak wrote: It looks like a simple bad reference name: On this line: * Fix the |psql|  commands |\sf| and |\ef| to handle SQL-language functions that have SQL-standard function bodies

Re: Tightening the trust auth advice

On 1/12/23 4:32 AM, Magnus Hagander wrote: The page at https://www.postgresql.org/docs/current/auth-trust.html goes through some length to explain why Trust is sometimes a good idea. Is it really though? And in particular, aren't there

Re: 'value' has special behaviour in alter system

On 12/15/22 10:50 AM, David G. Johnston wrote: On Thu, Dec 15, 2022 at 4:45 AM PG Doc comments form mailto:nore...@postgresql.org>> wrote: The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/sql-altersystem.html

Re: No multi range functions on version 12

On 12/15/22 6:46 AM, Magnus Hagander wrote: On Thu, Dec 15, 2022 at 12:45 PM PG Doc comments form mailto:nore...@postgresql.org>> wrote: The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/rangetypes.html

Re: Usability ideas: text width and headers that are links

Hi, Thanks for the suggestions. Comments inline: On 10/21/22 9:54 AM, Niels Bom wrote: Hi! I have 2 small ideas to improve the usability of the PostgreSQL documentation. I'm looking at v15 (1) mostly. Idea 1: Give the text width of the main content a max width. Why? Can you please provide

Re: pl Lua

On 10/17/22 6:03 AM, PG Doc comments form wrote: The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/external-pl.html Description: Your page, https://www.postgresql.org/docs/15/external-pl.html Please include another, active Lua binding

Re: Search engine linking to latest docs

On 7/25/22 6:08 PM, Trevor Gross wrote: Hey all, I think the PG community is pretty aware that there are some issues with search engines taking users to the right versions of the docs. You google something simple like "postgres drop column" and the first postgresql.org

Re: documentation on HOT

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 section (or subsection). As I mentioned in my previous post, given HOT

Re: Can we still dump version 7?

On 5/31/22 12:21 PM, Tom Lane wrote: "Jonathan S. Katz" writes: On 5/31/22 10:55 AM, Tom Lane wrote: 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

Re: Can we still dump version 7?

On 5/31/22 10:55 AM, Tom Lane wrote: "Daniel Westermann (DWE)" writes: 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.html Ugh, missed that, thanks for

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

On 5/31/22 8:35 AM, Magnus Hagander wrote: On Tue, May 31, 2022 at 2:29 PM Daniel Westermann (DWE) > wrote: Hi, I just came across this: "Also, specify -A md5 or -A password so that the default trust authentication mode is not

Re: documentation on HOT

On 2/6/22 8:56 PM, David G. Johnston wrote: On Sun, Feb 6, 2022 at 6:08 PM Jonathan S. Katz <mailto:jk...@postgresql.org>> wrote: Given the importance of HOT, it seems like this would be a good topic to document. I would suggest something higher-level for gene

documentation on HOT

Hi, While working on the 2020-02-10 release announcement, in order to better describe one of the fixes, I tried to find a reference in the docs that described what HOT is, how it works, etc. in a user-friendly manner. This lead me to the acronyms page[1], which lead me to a document in the

Re: missing a white space in the last sentence of 51.6. Executor

On 1/17/22 2:02 PM, Tom Lane wrote: PG Doc comments form writes: The last sentence of 51.6. Executor appears: "...feeding that up toModifyTable to perform the insertion." Hm, the space is definitely there in the source file: A simple INSERT ... VALUES command creates a trivial

Re: Add TypeScript driver

On 1/4/22 2:40 AM, PG Doc comments form wrote: The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/external-interfaces.html Description: Hi. I am Eray Hanoglu, author of postgresql-client javascript driver written in TypeScript

Re: ORDER BY in materialized view example?

On 11/23/21 12:44 PM, Tom Lane wrote: Peter Eisentraut writes: On 23.11.21 07:18, Maciek Sakrejda wrote: An example in the materialized view documentation [1] includes an ORDER BY clause without a clear reason. Does it help build the index more efficiently? I suppose it's also sort of like a

Re: I came here to determine how much storage a boolean variable uses

On 8/30/21 11:31 AM, David G. Johnston wrote: > On Sun, Aug 29, 2021 at 11:59 PM PG Doc comments form > mailto:nore...@postgresql.org>> wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/13/datatype.html >

Re: Use of the word master

On 8/5/21 2:26 PM, Dave Cramer wrote: > PostgreSQL: Documentation: 13: 30.1. Publication > > > > "A /publication/ can be defined on any physical replication master." > > I would propose "any physical replication

Re: Git is not an acronym

On 6/10/21 7:40 AM, Daniel Gustafsson wrote: > Commit 651377933e031 cleaned up references to CVS replacing them with Git. > Replacing CVS with Git in acronyms.sgml seems a bit incorrect though as Git > isn't an acronym (but CVS is, hence the original item replaced). We also > never > refer to

Re: failed to connect to PostgreSQL server on "db01:5432" using INET socket

Hi, On 5/24/21 12:45 AM, Moin Akther wrote: > Dear Team, > >   > > We are getting below error logs from pgpool. > >   > > May 18 07:48:31 pgpool[22685]: [7-1] 2021-05-18 07:48:31: pid 22685: > LOG: failed to connect to PostgreSQL server on "db01:5432" using INET socket > May 18 07:48:31

Re: pgpool: APPARENT DEADLOCK!!! Complete Status: Managed Threads: 3 Active Threads: 3

Hi Moin, On 5/18/21 3:30 AM, Moin Akther wrote: > Dear Team, > >   > > We are facing issue whenever application is connecting to pgpool 4^th Node. This email address is for contributing to the PostgreSQL documentation[1]. The Pgpool project provides contact information on reporting issues

Re: Link t the souce code

On 5/6/21 6:05 PM, Tom Lane wrote: > Alvaro Herrera writes: >> I agree -- if the user wanted packages, they would not be reading that >> page of the docs. I'd just have it point to the same page that the >> download page points to for source downloads, not a version-specific >> one, as in the

Re: mingw.org fails to load anything of value

On 4/4/21 9:30 PM, Michael Paquier wrote: > On Sun, Apr 04, 2021 at 09:47:08AM -0400, Jonathan S. Katz wrote: >> Diving deeper while updating the links, I stumbled across this note: >> >> "The MinGW.org web‑site is undergoing an overhaul, whilst in the process >>

Re: mingw.org fails to load anything of value

On 4/4/21 9:30 AM, Jonathan S. Katz wrote: > On 4/3/21 7:01 AM, PG Doc comments form wrote: >> The following documentation comment has been logged on the website: >> >> Page: https://www.postgresql.org/docs/13/installation-platform-notes.html >> Description: >>

Re: mingw.org fails to load anything of value

On 4/3/21 7:01 AM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/13/installation-platform-notes.html > Description: > > 16.7.4. MinGW/Native Windows refers to the site http://www.mingw.org which > for

Re: Documentation: 21.5. Default Roles

On 4/2/21 9:11 AM, Stephen Frost wrote: > Greetings, > > * Jonathan S. Katz (jk...@postgresql.org) wrote: >> Thanks Stephen! Do we have any additional follow up on the pgweb side? > > Yes and no. :) > > Once the next set of minor releases is pushed out, I'll dou

Re: Documentation: 21.5. Default Roles

On 4/1/21 3:34 PM, Stephen Frost wrote: > Greetings, > > * Stephen Frost (sfr...@snowman.net) wrote: >> I've written a patch to begin to make this change and sent it into >> -hackers for comments, thread is here: >> >> https://postgr.es/m/20201120211304.gg16...@tamriel.snowman.net > > Just to

Re: Update to reflect that TLS1 and TLSv1.1 are now deprecated

On 3/24/21 5:49 AM, Daniel Gustafsson wrote: > The recently published RFC 8996 deprecates the use of TLSv1 and TLSv1.1, the > attached rewords where we say our default of 1.2 is industry best practice > with > a link to the authoritative source. I would s/as of/stated in/ and add a comma after

Re: scram-sha-256 authentication

On 1/4/21 12:04 PM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/11/auth-password.html > Description: > > How do you encode a plain password to the corresponding SCRAM-SHA-256 > encryption? Using

Re: The sub-categories do not have anchors on this page

On 12/17/20 10:11 AM, David G. Johnston wrote: > On Thu, Dec 17, 2020 at 8:01 AM Bruce Momjian > wrote: > > On Thu, Dec 10, 2020 at 05:59:15PM -0300, Álvaro Herrera wrote: > > On 2020-Dec-10, Steven Pousty wrote: > > > > > They certainly do at the top of

Re: link may be broken

On 12/4/20 5:39 AM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/13/index.html > Description: > > Hello, > > the following page: > > https://www.postgresql.org/about/featurematrix/detail/340/ > >

Re: Possible Example Error in Documentation

On 11/5/20 7:37 PM, Tom Lane wrote: > PG Doc comments form writes: >> The following documentation comment has been logged on the website: >> Page: https://www.postgresql.org/docs/12/plpgsql-transactions.html >> Description: > >> We are using Postgres 12. When I use the example given for >>

Re: Version 13 documentation layout is harder to read than version 12

On 9/29/20 3:00 PM, Tom Lane wrote: > Niels Andersen writes: >> 2. Is there a middle ground? >> * Version 12 had 6 columns, version 13 has one. >> * Could we have fewer columns? What if we had 3 columns: One for >> operator or function, one for the details and description, and

Re: Another modest proposal for docs formatting: catalog descriptions

On 6/1/20 6:57 PM, Tom Lane wrote: > =?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= writes: >> I have spotted this change recently at progress monitoring devel docs ( >> https://www.postgresql.org/docs/devel/progress-reporting.html#CREATE-INDEX-PROGRESS-REPORTING). >> Current version seems a little chaotic

Re: Another modest proposal for docs formatting: catalog descriptions

On 5/10/20 2:03 PM, Jonathan S. Katz wrote: > On 5/10/20 12:27 PM, Tom Lane wrote: >> Just FTR, here's a complete patch for this. > > Cool. I'll play around with it tonight once I clear out release work. > Per upthread reference, I believe you've become a CSS maven yourself.

Re: Another modest proposal for docs formatting: catalog descriptions

On 5/10/20 12:27 PM, Tom Lane wrote: > Just FTR, here's a complete patch for this. Cool. I'll play around with it tonight once I clear out release work. Per upthread reference, I believe you've become a CSS maven yourself. > I successfully regenerated > the column names, types, and ordering

Re: Another modest proposal for docs formatting: catalog descriptions

On 5/6/20 5:18 PM, Alvaro Herrera wrote: > Hello > > I think the recent changes to CSS might have broken things in the XSLT > build; apparently the SGML tooling did things differently. Compare the > screenshot of tables 67.2 and 67.3 ... 9.6 on the left, master on the > right. Is the latter

Re: Another modest proposal for docs formatting: catalog descriptions

On 5/5/20 7:42 PM, Tom Lane wrote: > Here's a really quick-n-dirty prototype patch that just converts the > pg_aggregate table to the proposed style, plus a screenshot for those > who don't feel like actually building the docs with the patch. Not opposed to building the docs, but the screenshot

Re: Another modest proposal for docs formatting: catalog descriptions

On 5/4/20 9:52 PM, Tom Lane wrote: > As of HEAD, building the PDF docs for A4 paper draws 538 "contents > ... exceed the available area" warnings. While this is a nice step > forward from where we were (v12 has more than 1500 such warnings), > we're far from done fixing that issue. > > A large

Re: Documentation: 21.5. Default Roles

On 4/28/20 2:19 PM, Magnus Hagander wrote: > On Sat, Apr 25, 2020 at 1:38 AM Jonathan S. Katz <mailto:jk...@postgresql.org>> wrote: > > On 4/9/20 11:45 PM, Bruce Momjian wrote: > > On Thu, Apr  9, 2020 at 08:47:56PM -0400, Jonathan Katz wrote: > >>

Re: List of pages from versions 9, 10, and 11 that don't exist in "current"

On 4/25/20 1:12 PM, Michael Christofides wrote: > Hi there, > > Does anyone have an easy way of seeing which pages from the 9.x, 10, > or 11 docs don't have a "current" version? I don't have an easy way, but I have a pedantic way: 1. Set up the pgweb app[1] 2. Set up the requirements for the

Re: Documentation: 21.5. Default Roles

address, i.e. the new page. If it is, we issue a 301 (permanent redirecTt). - If it's still not found, we abort. I believe this gives us the desired behavior. Thoughts on the patch? Thanks, Jonathan From e2120f0a80697d13dc6d951f363d01feb60c9b9d Mon Sep 17 00:00:00 2001 From: "Jonathan S. Kat

Re: PDF documentation bug: different table columns overlap and are unreadable

On 4/17/20 3:37 AM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/index.html > Description: > > In the PDF documentation, some table columns overflow and overlap with the > next column. This makes

Re: Developer FAQ / What information is available to learn PostgreSQL internals?

On 4/16/20 4:20 AM, Marc Rechté wrote: > > https://wiki.postgresql.org/wiki/Developer_FAQ > > This link is dead: introduction to Hacking PostgreSQL - With lots of > code review! > https://linux.org.au/conf/2007/att_data/Miniconfs(2f)PostgreSQL/attachments/hacking_intro.pdf It appears that is

Re: pre-requiste for installation

On 4/12/20 8:21 AM, Ankush Chawla wrote: > hi  > > what is the pre-requiste packages for Postgres Installation on SUSE Linux > > I have already transferred .run file > > What would be pre-requiste package, hardware or software requirements , > any readme available? I believe these are listed

Re: Documentation: 21.5. Default Roles

On 4/9/20 4:57 PM, Bruce Momjian wrote: > On Thu, Feb 6, 2020 at 10:59:09AM -0500, Jonathan Katz wrote: >> On 2/6/20 12:11 AM, Bruce Momjian wrote: >>> On Tue, Feb 4, 2020 at 11:31:19AM -0500, Jonathan Katz wrote: > Using this feature to handle the rename of a file *between* major >

Re: Duplicating website's formatting in local doc builds

On 2/14/20 8:56 PM, Peter Geoghegan wrote: > On Fri, Feb 14, 2020 at 5:51 PM Tom Lane wrote: >> Hm, I wouldn't go into that much detail; it'd likely soon be out of >> date anyway. I had in mind something more like "If the STYLE=website >> option is used, the generated HTML files will include

Re: Duplicating website's formatting in local doc builds

On 2/14/20 6:06 PM, Tom Lane wrote: > "Jonathan S. Katz" writes: >> To load the webfont, the "main.css" file uses a CSS "@import" >> instruction, which has a limitation that it can only be used as the top >> of the file. As main.css is not th

Re: Duplicating website's formatting in local doc builds

On 2/11/20 10:56 PM, Jonathan S. Katz wrote: > On 2/11/20 3:49 PM, Jonathan S. Katz wrote: >> On 2/11/20 3:41 PM, Peter Geoghegan wrote: >>> On Tue, Feb 11, 2020 at 11:40 AM Jonathan S. Katz >>> wrote: >>>> Anyway, attached is a first attempt at a patch.

Re: Duplicating website's formatting in local doc builds

On 2/11/20 3:49 PM, Jonathan S. Katz wrote: > On 2/11/20 3:41 PM, Peter Geoghegan wrote: >> On Tue, Feb 11, 2020 at 11:40 AM Jonathan S. Katz >> wrote: >>> Anyway, attached is a first attempt at a patch. I tried a few different >>> variations but in my quick rev

Re: Duplicating website's formatting in local doc builds

On 2/11/20 3:41 PM, Peter Geoghegan wrote: > On Tue, Feb 11, 2020 at 11:40 AM Jonathan S. Katz > wrote: >> Anyway, attached is a first attempt at a patch. I tried a few different >> variations but in my quick review of it, I could not figure out how to >> make a XSLT

Re: Duplicating website's formatting in local doc builds

On 2/11/20 2:32 PM, Tom Lane wrote: > "Jonathan S. Katz" writes: >> On 2/11/20 1:37 PM, Tom Lane wrote: >>> I also wonder why duplicating the website's style isn't the default. >>> Doesn't seem like having authors optimize for some other style

Re: Duplicating website's formatting in local doc builds

On 2/11/20 1:37 PM, Tom Lane wrote: > I also wonder why duplicating the website's style isn't the default. > Doesn't seem like having authors optimize for some other style is > what we really want. Oh, and specifically for this, my guess is because it requires one to make a call over a network

Re: Duplicating website's formatting in local doc builds

On 2/11/20 1:37 PM, Tom Lane wrote: > I'm wondering how to do $SUBJECT. The fine manual suggests > > make STYLE=website html > > but what I'm getting here with that is not a very close approximation > of what I see at postgresql.org. It's closer than the default, > but it's not the same

Re: Documentation: 21.5. Default Roles

On 2/6/20 12:11 AM, Bruce Momjian wrote: > On Tue, Feb 4, 2020 at 11:31:19AM -0500, Jonathan Katz wrote: >>> Using this feature to handle the rename of a file *between* major >>> versions, thus leaving the changes in master, should be safe (as long >>> as we add an entry to that table in pgweb).

Re: Documentation: 21.5. Default Roles

On 2/4/20 3:34 AM, Magnus Hagander wrote: > On Mon, Feb 3, 2020 at 9:59 PM Jonathan S. Katz wrote: >> So, if there was something done to redirect people from specific >> deprecated documentation pages historically, it was before my time. Most >> of the redirects have bee

Re: Documentation: 21.5. Default Roles

On 2/3/20 3:42 PM, Bruce Momjian wrote: > On Thu, Jan 23, 2020 at 07:12:08PM -0500, R Ransbottom wrote: >> On Mon, Jan 20, 2020 at 12:23:48PM +0900, Ian Barwick wrote: >>> On 2020/01/19 12:56, R Ransbottom wrote: >> I would hope to find correct documentation somewhere--that somewhere >> >>>

Listing Drivers in the Docs (was: "Re: Postgres.js driver - for Node.js")

Hi, For this first round, going to truncate a bit of Stephen's thoughts (sorry Stephen) just to cover where we are at: On 1/9/20 12:00 PM, Stephen Frost wrote: > Greetings, > > * Jonathan S. Katz (jk...@postgresql.org) wrote: >> On 1/8/20 7:59 PM, Tom Lane wrote: >>> H

Re: Postgres.js driver - for Node.js

On 1/8/20 7:59 PM, Tom Lane wrote: > "Jonathan S. Katz" writes: >> On 1/8/20 7:00 PM, Jonathan Buhacoff wrote: >>> I'm wondering if the short list in the documentation [2] could be >>> replaced with a link to the corresponding wiki page [1] ? > >> ..

Re: Postgres.js driver - for Node.js

On 1/8/20 7:00 PM, Jonathan Buhacoff wrote: > I'm wondering if the short list in the documentation [2] could be > replaced with a link to the corresponding wiki page [1] ? >> [1] https://wiki.postgresql.org/wiki/List_of_drivers#Drivers >> [2]

Re: Postgres.js driver - for Node.js

On 1/8/20 3:06 PM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > I recently finished a fast, 0 dependency driver for Node.js with a very user > friendly api. Congratulations! > I think would be great to include in the documentation and the

Re: legacy assumptions

Hi, On 11/25/19 12:47 PM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/datatype-json.html > Description: > > I'm wondering if this one line of section 8.14 JSON Types >

Re: I'm surprised to see the word master here

On 10/2/19 7:39 AM, Chris Travers wrote: > > > On Wed, Oct 2, 2019 at 12:57 PM Erikjan Rijkers > wrote: > > On 2019-10-02 12:46, Peter Eisentraut wrote: > > On 2019-10-02 10:21, Magnus Hagander wrote: > >> Exactly. Both might be accurate, but one comes with a

Re: Formatting of warning about using ident

On 7/22/19 10:09 AM, Tom Lane wrote: > Peter Eisentraut writes: >> In general, I would argue in favor of fewer "note", "warning", etc. >> Some documentation pages are now just a sequence of "note"s and little >> proper text. If the normal text properly explains a topic and its pros >> and cons,

Re: Ambiguous language in Table 8.13. Special Date/Time Inputs [EXT]

On 7/10/19 6:13 AM, David Harper wrote: >> I actually agree with your opinion that "midnight" is fine. >> That text has been that way for over fifteen years[1], and >> nobody's complained before that it was ambiguous. > > Conversely, how many users over the past fifteen years have read that

Re: TOC: List of Figures

On 7/8/19 4:21 PM, Daniel Gustafsson wrote: >> On 8 Jul 2019, at 22:10, Tom Lane wrote: > >> let's wait till there's a >> meaningful number of figures and then reconsider whether there's use in >> a list of them. It's not like it will be any harder to make that change >> in a year or two than

Re: TOC: List of Figures

On 7/2/19 4:43 AM, Daniel Gustafsson wrote: >> On 2 Jul 2019, at 10:13, Jürgen Purtz wrote: > >> After the integration of figures into the documentation it may be helpful to >> extent the TOC with a 'List of Figures'. Any opinion? > > +1, I think we should. +1 > >> The alternative is a

Re: Add XSL stylesheet to fix up SVG files

On 6/20/19 4:32 AM, Peter Eisentraut wrote: > On 2019-06-11 13:19, Peter Eisentraut wrote: >> Commit 29046c44f36099f4c979b1491fcf27db2f9184f9 manually edited the SVG >> file generated by Ditaa, which was kind of what we wanted to avoid >> having to do. Here is an automated way to take care of the

Re: graphviz file extension

On 5/24/19 8:28 AM, Joe Conway wrote: > On 5/24/19 3:08 AM, Peter Eisentraut wrote: >> It has come to my attention that the preferred file extension for >> graphviz files is .gv rather than the .dot we are using. So I propose >> to change that for the one file we have so far (gin.dot) before we

Re: some grammar fixes for docs

On 5/16/19 7:32 PM, Michael Paquier wrote: > On Thu, May 16, 2019 at 05:11:37PM +0300, Liudmila Mantrova wrote: >> I have noticed imperfect grammar in a couple of sgml files, please consider >> a small patch (attached). > > Thanks, Liudmila for caring about such matters. > >> >> -

Re: a small fix for Release notes 11.3

On 5/16/19 10:17 AM, Liudmila Mantrova wrote: > Hello, > > Please consider a mini-patch for 11.3 release notes that fixes > pg_dump-related wording and also makes Jonathan's name consistent with > how it's listed in contributors list. I am flattered by your attention to detail around my name,

Additional "Creating a Cluster" Guidance for Windows Users

Hi, Per the last update release[1] I was going through some of our documentation around creating clusters and noticed that we may want to provide a bit more guidance around creating clusters on Windows: https://www.postgresql.org/docs/current/creating-cluster.html i.e.: "Because the data

Re: Why 'infinity' is not in range '[2019-01-02, infinity]'?

On 4/29/19 12:12 PM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/11/rangetypes.html > Description: > > Hi. > > May I read this: > > But [today,infinity] means something different from

Re: SET ROLE documentation not entirely correct

On 4/26/19 3:04 PM, Jonathan S. Katz wrote: > On 4/25/19 6:54 PM, Joe Conway wrote: >> On 4/25/19 5:59 PM, Jonathan S. Katz wrote: >>> On 4/25/19 5:26 PM, Joe Conway wrote: >>>> >>>> Is there any written instruction anywhere with guidance on how t

Re: Documentation for partitioned indexes?

On 4/26/19 2:53 PM, Alvaro Herrera wrote: > On 2019-Apr-26, Tom Lane wrote: > >> We appear to have a fair amount of support now for operations like >> constructing a partitioned index piecemeal, e.g. adding indexes >> to the partitions one at a time and then attaching them to a >> parent

Re: SET ROLE documentation not entirely correct

On 4/25/19 6:54 PM, Joe Conway wrote: > On 4/25/19 5:59 PM, Jonathan S. Katz wrote: >> On 4/25/19 5:26 PM, Joe Conway wrote: >>> >>> Is there any written instruction anywhere with guidance on how the SVGs >>> should be made? >> >> https://git.post

Re: SET ROLE documentation not entirely correct

On 4/25/19 5:26 PM, Joe Conway wrote: > > Is there any written instruction anywhere with guidance on how the SVGs > should be made? https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=doc/src/sgml/images/README; but I would suggest we had some guidance on how to ensure the image stays

Re: SET ROLE documentation not entirely correct

On 4/25/19 5:22 PM, Jonathan S. Katz wrote: > On 4/25/19 4:52 PM, Jonathan S. Katz wrote: >> On 4/25/19 3:20 PM, Joe Conway wrote: >>> On 4/25/19 3:06 PM, Stephen Frost wrote: >>>> Greetings, >>>> >>>> * Tom Lane (t...@sss.pgh.pa.us) wrote: &g

Re: SET ROLE documentation not entirely correct

On 4/25/19 4:52 PM, Jonathan S. Katz wrote: > On 4/25/19 3:20 PM, Joe Conway wrote: >> On 4/25/19 3:06 PM, Stephen Frost wrote: >>> Greetings, >>> >>> * Tom Lane (t...@sss.pgh.pa.us) wrote: >>>> Joe Conway writes: >>>>> On 4/25/19

Re: SET ROLE documentation not entirely correct

On 4/25/19 3:20 PM, Joe Conway wrote: > On 4/25/19 3:06 PM, Stephen Frost wrote: >> Greetings, >> >> * Tom Lane (t...@sss.pgh.pa.us) wrote: >>> Joe Conway writes: On 4/25/19 1:08 PM, Joe Conway wrote: > There is one image which can be used as an example though: >

Re: Typo

On 4/10/19 12:30 PM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/11/sql-createfunction.html > Description: > > I have noted that it seems not convenient. > " > Writing > SECURITY DEFINER > Functions

  1   2   >