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: 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: 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: 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 pgsql

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: 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. +1

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

clarifying trigger/rule behavior on logical replication subscribers

ng to find this 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 Subj

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 i

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 back-end

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 OpenPGP_signatu

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: 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 here

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 [2

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 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

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 of the

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 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 and

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 s

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 it

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 ho

Re: A minor bug in doc. Hovering over heading shows # besides it.

On 7/18/24 1:59 PM, Daniel Gustafsson wrote: On 18 Jul 2024, at 15:49, Tom Lane wrote: Daniel Gustafsson writes: While not a standard the pilcrow [0] is, AFAICT from a bit of looking at other docs, commonly used for this. There is a lot of variability though so whichever we choose it will be

Re: Is this still accurate?

Hi,On Jan 5, 2018, at 1:33 PM, Steve Atkins wrote:On Jan 5, 2018, at 10:00 AM, Stephen Frost wrote:Greetings,* Moser, Glen G (glen.mo...@charter.com) wrote:That's really the gist of the concern from a team member of mine.  Not that the 4TB number is wrong but that it could be misleading to assume

Re: Is this still accurate?

Hi, > On Jan 6, 2018, at 9:45 AM, Magnus Hagander wrote: > > > > On Fri, Jan 5, 2018 at 8:09 PM, Jonathan S. Katz <mailto:jk...@postgresql.org>> wrote: > Hi, > >> On Jan 5, 2018, at 1:33 PM, Steve Atkins > <mailto:st...@blighty.com>> wrote:

Re: Can we only add values to enums?

> On Mar 15, 2018, at 11:33 PM, Euler Taveira wrote: > > 2018-03-12 20:28 GMT-03:00 PG Doc comments form : >> I need to add a value to an enum, so I found this page, which answered my >> question. However, I found it quite confusing that it only documents adding >> a value. I would expect it to

Re: Can we only add values to enums?

> On Mar 16, 2018, at 10:48 AM, Tom Lane wrote: > > "Jonathan S. Katz" writes: >> I would say that’s the exact reason why it should be documented, >> so it’s clear that it was by design. > > Seems reasonable. Maybe something in 8.7.4 enum implementation

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

> On Mar 28, 2018, at 9:32 PM, Peter Eisentraut > wrote: > > On 3/28/18 21:30, Peter Eisentraut wrote: >> On 3/23/18 08:56, Daniel Westermann wrote: >>> 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/do

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

> On Mar 28, 2018, at 9:47 PM, Peter Eisentraut > wrote: > > On 3/28/18 21:36, Jonathan S. Katz wrote: >> >>> On Mar 28, 2018, at 9:32 PM, Peter Eisentraut >>> >> <mailto:peter.eisentr...@2ndquadrant.com>> wrote: >>>> Yeah, t

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

> On Apr 3, 2018, at 10:55 AM, Peter Eisentraut > wrote: > > On 4/3/18 09:12, Magnus Hagander wrote: >> I've pushed the fix and reloaded the 10 docs. I have not reloaded >> earlier branches yet, but I'd be interested in some people reviewing a >> bunch of pages in the 10 docs mainly to see if (

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

> On Apr 4, 2018, at 8:59 PM, Peter Eisentraut > wrote: > > On 4/4/18 09:21, Jonathan S. Katz wrote: >> The only thing I saw (and this may be something to look at the SGML >> source) was some blocks that looked overly indented, but it was consistent >> across

Re: Pg_dumpall

Hi, > On Apr 7, 2018, at 10:55 AM, PG Doc comments form > wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/static/backup-dump.html > Description: > > "The basic usage of this command is: > > pg_dumpall > outfile > The

Re: Start with [ , end with )

> On Apr 23, 2018, at 8:37 PM, Mike Toews wrote: > > On 24 April 2018 at 01:00, PG Doc comments form > wrote: >> 8.17.2. Examples >> >> CREATE TABLE reservation (room int, during tsrange); >> INSERT INTO reservation VALUES >>(1108, '[2010-01-01 14:30, 2010-01-01 15:30)'); >>

Re: Appendix A. PostgreSQL Error Codes

> On Apr 28, 2018, at 5:11 PM, Tom Lane wrote: > > "Andy Dossett" writes: >> The use case is pretty simple; my system has thrown an SQL error code, I >> want to know what it means. >> Having the list in 'order by sqlstate' sequence would save me from having to >> hunt up and down the list. And

Re: documentation synopsis grammar

> On May 11, 2018, at 8:15 PM, Tom Lane wrote: > > "David G. Johnston" writes: >> I'm suspecting that our best bet is leave the notation page a bit vague and >> just clear up confusion when it arises. The example above, while probably >> technically incorrect, is, I'm reasonably certain, commo

Re: Release note trimming: another modest proposal

> On Aug 5, 2018, at 6:57 PM, Tom Lane wrote: > > We've been around on this before, I know, but I got annoyed about it > again while waiting around for test builds of the back-branch > documentation. I think that we need some policy about maintaining > back-branch release notes that's not "keep

Re: Release note trimming: another modest proposal

> On Aug 6, 2018, at 11:09 AM, Tom Lane wrote: > > "Jonathan S. Katz" writes: >>> On Aug 5, 2018, at 6:57 PM, Tom Lane wrote: >>> ... We could discuss ways >>> of making a complete release-note archive available somewhere, >>> if "

Re: Release note trimming: another modest proposal

> On Aug 6, 2018, at 11:47 AM, Tom Lane wrote: > > "Jonathan S. Katz" writes: >> Though thinking on this further, we’d probably want to maintain the URLs >> that have been generated through the years so they don’t all 404 at once. >> That would require hav

Re: Release note trimming: another modest proposal

> On Aug 6, 2018, at 12:55 PM, Tom Lane wrote: > > "Jonathan S. Katz" writes: >> FWIW I’m thinking of something like: > >> `/docs/release-notes/release-X-Y(-Z)?.html` > >> and have them all live there. Of course the docs themselves would still >

Re: Release note trimming: another modest proposal

> On Aug 6, 2018, at 3:27 PM, Tom Lane wrote: > > I wrote: >> Hm, so the only objection I can think of is that this results in the old >> release notes only being available on the website; there's no other way >> to access them, short of digging around in the git repo. But maybe that's >> enoug

Re: Release note trimming: another modest proposal

> On Aug 6, 2018, at 3:37 PM, Tom Lane wrote: > > "Jonathan S. Katz" writes: >>> On Aug 6, 2018, at 3:27 PM, Tom Lane wrote: >>> Actually, a concrete reason why that might not be good is that it results >>> in having a single point of failure: o

Re: how to modify the navfooter

> On Aug 7, 2018, at 6:21 PM, Richard Swagerman > wrote: > > Where is the content of the navfooter established? > I would like to make some modifications to this footer, but I am unable to > figure out where the source that generates it. > > I am building the documentation following the instr

Re: 25.3. Continuous Archiving : Unix examples with Windows-style variables %-$

Hi, > On Aug 23, 2018, at 5:54 AM, PG Doc comments form > wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.4/static/continuous-archiving.html > Description: > > Most examples in "25.3. Continuous Archiving and Point-in-

Re: "System roles" mentioned in psql documentation

> On Aug 23, 2018, at 3:58 AM, Michael Paquier wrote: > > Hi all, > > I have noticed that psql documentation mentions "system roles", however > in all other parts of the docs, we use the term "default roles". > Shouldn't we make this term more consistent and also add a link to the > table descr

Re: retroactive pg10 relnotes: sequence changes

On Aug 28, 2018, at 1:02 PM, Magnus Hagander wrote:On Tue, Aug 28, 2018 at 6:34 PM, Alvaro Herrera  wrote:HelloA customer of ours was taken by surprise by a change in Postgres 10 on atrial upgrade from 9.6.  They were using sequences from SERIAL colum

Re: retroactive pg10 relnotes: sequence changes

On Aug 28, 2018, at 1:09 PM, Jonathan S. Katz <jk...@postgresql.org> wrote:On Aug 28, 2018, at 1:02 PM, Magnus Hagander <mag...@hagander.net> wrote:On Tue, Aug 28, 2018 at 6:34 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote:HelloA customer of ours was taken by surprise by a

Proposed HTML Documentation Styles

Hi, As part of the effort to modernize the look and feel of PostgreSQL.org and associated web projects, Sarah & I have worked on applying the new styles to the documentation. The main goals of the project were: - To have the documentation styles match that of the main website - To make the docume

Re: Proposed HTML Documentation Styles

Hi Pavel, On 10/4/18 12:02 PM, Pavel Stehule wrote: > When I am going to document, then I see (about 0.5 sec) big PostgreSQL > logo. It is not pleasant effect. That's cache related - we won't need to worry about that on the production site. > > I don't like table style - middle vertical line i

Re: Proposed HTML Documentation Styles

On 10/4/18 12:28 PM, Alvaro Herrera wrote: > On 2018-Oct-04, Pavel Stehule wrote: > >> čt 4. 10. 2018 v 17:50 odesílatel Jonathan S. Katz >> napsal: >> >> When I am going to document, then I see (about 0.5 sec) big PostgreSQL >> logo. It is not pleasant ef

Re: Proposed HTML Documentation Styles

On 10/4/18 12:33 PM, Jonathan S. Katz wrote: > On 10/4/18 12:28 PM, Alvaro Herrera wrote: >> This TOC looks a bit odd, with those bold black elements amongst all >> that red: http://174.138.60.30/docs/10/static/ecpg.html I suppose these >> should just be bold witho

Re: Proposed HTML Documentation Styles

Hi Dean, On 10/4/18 3:41 PM, Dean Rasheed wrote: > On Thu, 4 Oct 2018 at 16:50, Jonathan S. Katz wrote: >> As part of the effort to modernize the look and feel of PostgreSQL.org >> and associated web projects, Sarah & I have worked on applying the new >> styles to the do

Re: Proposed HTML Documentation Styles

Hi Dean, On 10/11/18 3:01 AM, Dean Rasheed wrote: > On Thu, 11 Oct 2018 at 06:49, Dean Rasheed wrote: >> For example, attached are screenshots taken from my Android tablet > > For the record, that was a Samsung Galaxy Tab S2 8.0, with a screen > resolution of 2048x1536 and a device pixel ratio o

Re: Proposed HTML Documentation Styles

On 10/4/18 11:50 AM, Jonathan S. Katz wrote: > Hi, > > As part of the effort to modernize the look and feel of PostgreSQL.org > and associated web projects, Sarah & I have worked on applying the new > styles to the documentation. The main goals of the project were:

Re: Proposed HTML Documentation Styles

Hi Alexander, On 10/16/18 2:44 PM, Alexander Romanenko wrote: > I am having problem with distinguishing tables from the description body > without shadows. Without a shadow, stronger border and headings,  like > in old version, tables likes function parameter lists blends in with > description par

Re: Images in the official documentation

Hi Jürgen, On 11/14/18 8:36 AM, Jürgen Purtz wrote: > After many mails, F2F-discussions and some experiments - everything > without a concrete result - I hereby start a new initiative concerning > SVG tools. The attached PDF file describes my recommendation. The two > SVG files are examples for wo

Re: Documentation for create unique index is insuficient and (because of that) incorrect

On 11/19/18 9:05 PM, Bruce Momjian wrote: > On Tue, Oct 23, 2018 at 06:29:55PM +, PG Doc comments form wrote: >> The following documentation comment has been logged on the website: >> >> Page: https://www.postgresql.org/docs/11/static/indexes-unique.html >> Description: >> >> In https://www.pos

Re: Documentation for create unique index is insuficient and (because of that) incorrect

On 11/20/18 9:59 AM, Tom Lane wrote: > "Jonathan S. Katz" writes: >> On 11/19/18 9:05 PM, Bruce Momjian wrote: >>> On Tue, Oct 23, 2018 at 06:29:55PM +, PG Doc comments form wrote: >>>> In https://www.postgresql.org/docs/11/static/indexes-unique.html th

Re: Documentation for create unique index is insuficient and (because of that) incorrect

On 11/20/18 1:08 PM, Alvaro Herrera wrote: > On 2018-Nov-20, Tom Lane wrote: > >> So what I think I should do is reformulate that discussion to talk >> about making covering indexes with INCLUDE, and then mention in >> passing that you can also do it without that as long as you don't mind >> the p

Re: tickling the lesser contributor's withering ego

On 12/27/18 4:53 AM, Magnus Hagander wrote: > > > On Fri, Dec 21, 2018 at 4:17 PM Alvaro Herrera > wrote: > > On 2018-Dec-21, Tom Lane wrote: > > > Alvaro Herrera > writes: > > > I propose the following patch, w

Re: Release note trimming: another modest proposal

On 8/30/18 4:15 PM, Magnus Hagander wrote: > On Fri, Aug 10, 2018 at 1:38 AM, Peter Eisentraut > > wrote: > > On 06/08/2018 00:57, Tom Lane wrote: > > Anyway, I'd like to propose a compromise position that I don't think > > has been discussed b

Re: protocol-message-formats <- display format

On 1/8/19 2:33 PM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/11/protocol-message-formats.html > Description: > > Hi, > > It would improve the readability if we add further tabulation to the > descri

Re: protocol-message-formats <- display format

On 1/9/19 10:13 AM, Jonathan S. Katz wrote: > On 1/8/19 2:33 PM, PG Doc comments form wrote: >> The following documentation comment has been logged on the website: >> >> Page: https://www.postgresql.org/docs/11/protocol-message-formats.html >> Description: >>

Re: Font size of nested headlines counterintuitive

On 1/11/19 7:54 AM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/11/collation.html > Description: > > The font size of level 4 headlines (, e.g. "23.2.2.3. Creating New > Collation Objects") is remarkab

Re: Bug reporting guidelines order of instructions

On 1/18/19 4:06 PM, Joe Conway wrote: > On 1/17/19 9:29 AM, Alvaro Herrera wrote: >> On 2019-Jan-17, Magnus Hagander wrote: >> >>> Per the docs comment today, I will remove the notes about majordomo at >>> https://www.postgresql.org/docs/current/bug-reporting.html. >>> >>> However, this one also su

Re: Release note trimming: another modest proposal

On 1/25/19 6:46 PM, Bruce Momjian wrote: > On Fri, Jan 25, 2019 at 06:41:20PM -0500, Tom Lane wrote: >> Bruce Momjian writes: >>> I assume this means we would only keep the current release notes in the >>> git tree too, e.g. 11.0, 11.1, 11.2, etc. >> >> Yeah, I'd imagine that each branch would hav

Re: Release note trimming: another modest proposal

On 1/26/19 10:06 AM, Tom Lane wrote: > "Jonathan S. Katz" writes: >> The one "caveat" I will bring up is that once pushed and applied to the >> site, we would bring introduce a lot of 404s into the website. > > Hm. In principle we could probably insert

Re: Release Notes for PostgreSQL v10.4 is same as release 9.6.9

On 1/31/19 8:52 AM, Bruce Momjian wrote: > On Thu, Jan 31, 2019 at 02:07:41PM +, PG Doc comments form wrote: >> The following documentation comment has been logged on the website: >> >> Page: https://www.postgresql.org/docs/10/release-10-4.html >> Description: >> >> I could see the features, re

Re: Release note trimming: another modest proposal

On 2/4/19 11:12 AM, Tom Lane wrote: > "Jonathan S. Katz" writes: >> On 1/26/19 10:06 AM, Tom Lane wrote: >>> If I haven't heard objections, I'll see about making this happen >>> during the first week of Feb (after the CF closes, but before &

Re: Release note trimming: another modest proposal

On 2/4/19 4:25 PM, Tom Lane wrote: > "Jonathan S. Katz" writes: >> On 2/4/19 11:12 AM, Tom Lane wrote: >>> It's not quite clear to me what the policy would be for removing >>> back-branch links from this list when old versions drop out of support

Re: Release note trimming: another modest proposal

On 2/4/19 5:23 PM, Tom Lane wrote: > "Jonathan S. Katz" writes: >> On 2/4/19 4:25 PM, Tom Lane wrote: >>> After a bit more thought, I'm inclined to propose that the policy be >>> that we *don't* update the surviving back branches for branch retire

Re: Release note trimming: another modest proposal

On 2/5/19 1:02 AM, Andres Freund wrote: > Hi, > > On 2019-01-26 10:06:06 -0500, Tom Lane wrote: >> "Jonathan S. Katz" writes: >>> The one "caveat" I will bring up is that once pushed and applied to the >>> site, we would bring introduce a lot

Re: Release note trimming: another modest proposal

On 2/5/19 9:12 AM, Tom Lane wrote: > Anyway, if people want something resembling the old presentation, > I think the way to get there is to have some sort of aggregate > release notes in a separate place on the web site. We'd discussed > that briefly upthread, but no one's volunteered to push it

Re: Release note trimming: another modest proposal

On 2/5/19 11:37 AM, Tom Lane wrote: > I wrote: >> BTW, while we're thinking about this --- I remembered that as things >> stand, we've broken my historical practice of putting up first-draft >> minor release notes for people to look at if they choose. Those will >> now be in the newest back branch

Re: Release note trimming: another modest proposal

On 2/5/19 12:17 PM, Andres Freund wrote: > Hi, > > On 2019-02-05 12:10:57 -0500, Tom Lane wrote: >> Andres Freund writes: >>> On 2019-02-05 08:50:16 -0500, Jonathan S. Katz wrote: >>>> The original thought process was to _not_ do that given the effort, but

Re: Tutorial section of documentation: enhancements needed

Hi Laetitia, On 2/12/19 3:06 AM, Lætitia Avrot wrote: > To me, there are 2 options: > - either, we change the "Tutorial" name of that chapter, so millenials > don't think they will find a step by step doc on how to install, > configure and connect to Postgres and add a tutorial page (the name can

Responsive images in pgweb docs

s/gin.svg you find: From b4f94ee3b62d4eeec45cfa4fbba5375810d8ae59 Mon Sep 17 00:00:00 2001 From: "Jonathan S. Katz" Date: Sun, 31 Mar 2019 10:16:26 -0400 Subject: [PATCH] Modify SVGs to not have view boxes that can scale based on viewing container. This allows for responsive image viewing, particularly on the we

Re: Responsive images in pgweb docs

On 4/1/19 5:57 AM, Peter Eisentraut wrote: > On 2019-03-31 16:23, Jonathan S. Katz wrote: >> When testing the rendering of the images on the pgweb docs, I discovered >> that they are not responsive (see attached) and in its current state, >> basically makes any pag

Re: Responsive images in pgweb docs

On 4/1/19 8:22 AM, Peter Eisentraut wrote: > On 2019-04-01 13:23, Jonathan S. Katz wrote: >>> Image scaling is currently intentionally disabled for the HTML output >>> (see ignore.image.scaling in stylesheet-html-common.xsl). But if we >>> turn it on, then the images

Re: Clarity in partial index example.

ry. You're correct, the url = '/index.html' does not affect if the partial index is used in the example. Based on how the example is set up, I'd propose using the "url" parameter in both examples. I've attached a patch that does this, with some additional wording

Re: Clarity in partial index example.

On 4/3/19 6:30 PM, Tom Lane wrote: > "Jonathan S. Katz" writes: >> On 4/3/19 4:20 PM, PG Doc comments form wrote: >>> Maybe I am misunderstanding the concept here but url = '/index.html' doesn't >>> have any effect on this? If that's the c

Re: Responsive images in pgweb docs

oth the HTML build and with the import into pgweb with new patch, and it scaled correctly. Thanks, Jonathan From cc29aa43269ba7beb11a61aa93096698540af179 Mon Sep 17 00:00:00 2001 From: "Jonathan S. Katz" Date: Thu, 4 Apr 2019 12:21:38 -0400 Subject: [PATCH 2/2] Make pagelayout.svg sc

Re: Clarification to pg_upgrade docs on reverting to old cluster

On 4/5/19 8:26 AM, Magnus Hagander wrote: > > > On Thu, Apr 4, 2019 at 11:14 PM Daniel Gustafsson > wrote: > > Reading the pg_upgrade reference page, I get the feeling that one of the > bullets under "Reverting to old cluster" is a bit thin on detail to > be

initdb recommendations

ng point would be to ensure we call this out) Credits to Magnus for pointing this out, and Tom + Andrew D. for review before posting to list. Jonathan [1] https://www.postgresql.org/docs/current/creating-cluster.html From 1941d8e5c24f38798edd6a63b68a9687511f349c Mon Sep 17 00:00:00 2001 Fro

Re: initdb recommendations

On 4/5/19 4:58 PM, Peter Eisentraut wrote: > On 2019-04-05 18:11, Jonathan S. Katz wrote: >> (There could be an additional discussion about whether or not we want to >> change the default behavior for initdb, but I would suggest that a safe >> starting point would be to en

Re: initdb recommendations

On 4/8/19 8:25 AM, Peter Eisentraut wrote: > On 2019-04-05 18:11, Jonathan S. Katz wrote: >> + >> + We recommend using the -W, >> --pwprompt, >> + or --pwfile flags to assign a password to the >> database >> + superuser, and

Re: initdb recommendations

On 4/8/19 8:44 AM, Magnus Hagander wrote: > On Mon, Apr 8, 2019 at 2:41 PM Jonathan S. Katz <mailto:jk...@postgresql.org>> wrote: > > On 4/8/19 8:25 AM, Peter Eisentraut wrote: > > On 2019-04-05 18:11, Jonathan S. Katz wrote: > >> +    >

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

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: > https://git.postgresq

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 1:

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 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 sc

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: 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 partition

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: 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 [today,infinity

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 direct

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, but

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: 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 ad

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

  1   2   >