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

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 failur

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

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

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

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

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

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

> On Apr 4, 2018, at 8:59 PM, Peter Eisentraut > <peter.eisentr...@2ndquadrant.com> 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, b

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

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

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

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

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

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

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

Re: Can we only add values to enums?

> On Mar 16, 2018, at 10:48 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > > "Jonathan S. Katz" <jk...@postgresql.org> writes: >> I would say that’s the exact reason why it should be documented, >> so it’s clear that it was by design. > >

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

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 w

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

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

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

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

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 th

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

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,

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

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

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

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

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

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

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: Responsive images in pgweb docs

ML 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 scalable bas

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

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

Responsive images in pgweb docs

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

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 ima

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

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: 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 retirement.

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

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

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

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

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

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

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: 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 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/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/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: 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 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] ? > >> ..

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

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

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

  1   2   >