Re: Streaming Replication vs Logical

On 12.10.24 00:53, Paul A Jungwirth wrote: Our docs seem to contrast "streaming replication" to logical, but these are not really opposites. Sometimes when they say "streaming" they mean "physical". Probably this is historical: at first physical replication was the only kind of streaming we ha

Re: DocBook 5.2

I took another look at this issue, and found that no Red Hat distro is yet shipping DocBook 5.2; not even Fedora 40 which is bleeding edge. So I would have to obtain and manually install the relevant DTDs and style sheets, as would a lot of other contributors. I'm less familiar with the Debian ec

Re: DocBook 5.2

On 27.09.22 09:12, Jürgen Purtz wrote: Yeah, I think we'd have to convert all the supported versions to make this palatable. If the conversion is sufficiently automated, that might not be a big lift. (If it's*not* automated, I think the change would never get off the ground eve

Re: nested tags in glossary entries in html docs

On 25.04.24 13:24, Jürgen Purtz wrote: On 25.04.24 11:24, Alvaro Herrera wrote: On 2024-Apr-12, Erik Wienhold wrote: There's this bug[1] in the DocBook XSLT stylesheets. Looks like the fix[2] landed in 1.79.2 (latest version on Arch, Maybe one of these days we should get going wit

Re: nested tags in glossary entries in html docs

On 25.04.24 11:24, Alvaro Herrera wrote: On 2024-Apr-12, Erik Wienhold wrote: There's this bug[1] in the DocBook XSLT stylesheets. Looks like the fix[2] landed in 1.79.2 (latest version on Arch, Maybe one of these days we should get going with the migration to Docbook 5.x that Jürgen

Re: DocBook 5.2

Yeah, I think we'd have to convert all the supported versions to make this palatable. If the conversion is sufficiently automated, that might not be a big lift. (If it's*not* automated, I think the change would never get off the ground even for HEAD, because the docs are too much of a moving ta

Re: DocBook 5.2

On 05.09.22 14:15, Guillaume Lelarge wrote: Le lun. 5 sept. 2022 à 13:14, Alvaro Herrera a écrit : On 2022-Sep-05, Jürgen Purtz wrote: > - > + >    User-Defined Types OK, these seem quite significant changes that are likely to cause great pain.  So I

Re: DocBook 5.2

On 05.09.22 11:59, Daniel Gustafsson wrote: Will the markup be similar enough to not carry a significant risk of introducing pain for backpatching doc patches? There are many changes. Most of them are systematically and others are individual, which is more painful. To give you an impression wh

Re: DocBook 5.2

we have to act carefully to deliver (nearly) identical HTML, PDF, ... files as before. As a preview of the ongoing the actual README.md file is attached. Jürgen Purtz Migration of PG's documentation from DocBook 4.5 to DocBook 5.2 ===

DocBook 5.2

DocBook 5.2 is around the corner [1], we use DocBook 4.5 which is 'feature frozen' since 2006, and there are even ideas for DocBook 6.x [2]. I want to inform you that I'm working on an upgrade of our documentation to DocBook 5.2. Major steps have been done, but I need some more time before I c

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

data type cast, ...? * schema-level: table, index, view, materialized view, foreign table, sequence, constraint, function, procedure, trigger, operator, ...? -- Jürgen Purtz

Re: [PATCH] add link to domain data types section from locale documentation

; and the description below "columns") This selection is a bit arbitrary, I admit. Yours, Laurenz Albe Done at the proposed pages - and a few more. -- Jürgen Purtz diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index 98df74d0e1..8434bf6ba4 100644 --- a/doc/

Re: Headers for each index

do search in the page to find the available indexes. Thanks a ton! The look&feel has changed in version 14 in a way that hopefully matches your suggestion: https://www.postgresql.org/docs/14/indexes-types.html -- Jürgen Purtz

Re: Additional Chapter for Tutorial

done, or even whether you intend to continue with it. Thanks, Erik Peter changed the status to 'Returned with feedback' at the end of the last commit fest. I'm not absolutely sure, but my understanding is that the patch is rejected. -- Jürgen Purtz

Re: [PATCH] add link to domain data types section from locale documentation

ning the SQL and IP meaning may be helpful. -- Jürgen Purtz diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index 1b00e543a6..300a0d83d4 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -346,7 +346,8 @@ initdb --locale=sv_SE collation. (The b

Re: Additional Chapter for Tutorial

On 21.10.20 22:33, David G. Johnston wrote: I've begun looking at this and have included quite a few html comments within the patch.  However, the two main items that I have found so far are: One, I agree with Peter that this seems misplaced in Tutorial.  I would create a new Internals Chapte

Re: Change JOIN tutorial to focus more on explicit joins

On 22.10.20 17:14, Pavel Stehule wrote: Why do you use parenthesis for ON clause?  It is useless. SQL is not C or JAVA. Two more general answers: - Why do people use tabs, spaces, and newlines to format their code even though it's not necessary? SQL is a language to develop applications. A

Re: Change JOIN tutorial to focus more on explicit joins

On 22.10.20 01:40, David G. Johnston wrote: On Fri, Sep 4, 2020 at 2:36 AM Jürgen Purtz <mailto:juer...@purtz.de>> wrote: On 04.09.20 08:52, Peter Eisentraut wrote: > > For the remaining patch I have a couple of concerns: This patch should not be changing the for

Re: exceptions

On 21.10.20 18:17, Tom Lane wrote: PG Doc comments form writes: Description: 02000 no_data should read no_data_found Looks correct as stated to me. plpgsql's ERRCODE_NO_DATA_FOUND (P0002) is a different animal. regards, tom lane Yes, our documentation correlates

Re: Additional Chapter for Tutorial

On 10.09.20 18:26, Peter Eisentraut wrote: On 2020-09-02 09:04, Jürgen Purtz wrote: On 01.09.20 23:30, Peter Eisentraut wrote: It is mostly advanced low-level information that is irrelevant for someone starting up, That applies only to the VACUUM chapter. VACUUM and AUTOVACUUM are controlled

Re: Change JOIN tutorial to focus more on explicit joins

keys, I don't think we should imply that one of them is unprofessional and then leave it at that and give no further guidance. I think we should leave this out. Ok, deleted. -- Jürgen Purtz diff --git a/doc/src/sgml/query.sgml b/doc/src/sgml/query.sgml index e73e805ec4..413763691e 100644 ---

Re: Additional Chapter for Tutorial

On 01.09.20 23:30, Peter Eisentraut wrote: It is mostly advanced low-level information that is irrelevant for someone starting up, That applies only to the VACUUM chapter. VACUUM and AUTOVACUUM are controlled by a lot of parameters. Therefor the current documentation concerning the two mechan

Re: initdb - creating clusters

On 30.08.20 17:21, Tom Lane wrote: Do you have a feeling one way or the other about whether to repeat some of this text in each of the relevant sub-sections? I initially didn't want to do that, but thinking about how people consume the HTML docs, I'm afraid that anything not appearing on the sam

Re: Procedures

On 22.08.20 13:05, Robin Abbi wrote: On Fri, 21 Aug 2020 at 23:52, Bruce Momjian > wrote: I developed the attached patach for this.  Is this sufficient? Would it be appropriate to consider including some language with a similar information content to this "

Re: obsolete indexing method "rtree"

On 06.08.20 10:12, David G. Johnston wrote: On Thu, Aug 6, 2020 at 12:18 AM Jürgen Purtz <mailto:juer...@purtz.de>> wrote: > Why? Because it can hinder the learning process. FWIW I'd at least fixup comment.sgml to reference a current type.  And while in there

Re: obsolete indexing method "rtree"

Perhaps it's talking about a deficiency that was specific to the old rtree code. And sometimes even experts have to spend time thinking about the situation. Nevertheless, this is a tiny issue. Unfortunately I don't have the knowledge to modify the C-source and create a patch. -- Jürgen Purtz

obsolete indexing method "rtree"

pt of R-trees and not to the eliminated implementation. Isn't it time to disallow this syntax and remove all references and messages? The situation concerning index types, access methods, operator classes, and index related extensions is complicate enough and hard to explain to newcomers. Every simplification should be welcomed. -- Jürgen Purtz

Import an XML file

your pg_get_file function * a short excerpt of your file * the DDL of your table * what is your understanding of a 'cell'? Is this helpful: https://www.postgresql.org/docs/current/functions-xml.html ? Kind regards, Jürgen Purtz

Re: Add A Glossary

elf in 'Logger (process)' - new term: Base Backup -- Jürgen Purtz diff --git a/doc/src/sgml/glossary.sgml b/doc/src/sgml/glossary.sgml index 76525c6302..58e5071642 100644 --- a/doc/src/sgml/glossary.sgml +++ b/doc/src/sgml/glossary.sgml @@ -108,7 +108,7 @@ - Autovacuum +

Re: Additional Chapter for Tutorial

On 12.07.20 22:45, Daniel Gustafsson wrote: This patch no longer applies, due to conflicts in start.sgml, can you please submit a rebased version? ok. but I need some days.  juergen

Re: Add A Glossary

On 17.06.20 02:09, Alvaro Herrera wrote: On 2020-Jun-09, Jürgen Purtz wrote: Can you agree to the following definitions? If no, we can alternatively formulate for each of them: "Under discussion - currently not defined". My proposals are inspired by chapter 2.2 Concepts: "Tab

Re: some charts or graphs of possible permissions would be nice

evel. Is it worth to give more details? I don't think so. But it may be a good idea to follow Stephen's suggestion and put an introductory summary to the tutorial chapter. -- Jürgen Purtz

Re: Add A Glossary

ange to existing definition): "A computer that communicates with other computers over a network. This is sometimes used as a synonym for server. It is also used to refer to a computer where client processes run." -- Jürgen Purtz

Re: Change JOIN tutorial to focus more on explicit joins

On 20.05.20 23:56, Thomas Munro wrote: On Thu, May 21, 2020 at 1:37 AM PG Doc comments form wrote: The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/tutorial-join.html Description: The tutorial about joins makes the following statemen

Re: Add A Glossary

On 19.05.20 08:17, Laurenz Albe wrote: On Mon, 2020-05-18 at 18:08 +0200, Jürgen Purtz wrote: cluster/instance: PG (mainly) consists of a group of processes that commonly act on shared buffers. The processes are very closely related to each other and with the buffers. They exist altogether or

Re: Add A Glossary

ver architecture* or *host* in TCP/IP configuration. We cannot change such matter of course. I suggest to use both depending on the context, but with the same meaning: "real hardware, a container, or a virtual machine". -- Jürgen Purtz (PS: I added the docs mailing list)

Re: dot dot dot dot

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/tutorial-sql-intro.html Description: is wrong. The four dots are not really a part of the path. Don't use them literally. They indicate that you should use your local path inst

Re: Documentation - chapter 52, system catalogs

in the right one. But this is a huge change of the look-and-feel as well as for all technical stuff: HTML, CSS, bootstrap, Javascript, Ajax(?), ... . -- Jürgen Purtz

Re: Documentation - chapter 52, system catalogs

the title of 36.1. to "Overview" in correlation with "System Catalog". -- Jürgen Purtz diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index ce33df9e58..8854bda05f 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -6,6 +6,23

Re: Additional Chapter for Tutorial

e interested in its architecture than in its details. We shall offer an overview about the major PG components and strategies to beginners. -- Jürgen Purtz

Re: An XSLT example script

bers restart in every chapter for figures, examples, and tables (there is an additional table in the huge list of tables of this chapter: "Bit String Functions" after "Bit String Operators"). -- Jürgen Purtz

Re: An XSLT example script

On 21.04.20 20:10, Peter Eisentraut wrote: On 2020-04-14 10:03, Jürgen Purtz wrote: The example "XSLT Stylesheet for Converting SQL/XML Output to HTML" is tagged as , but it isn't a figure, it's an example script. It's not an example, it's an actual script that

Re: Additional Chapter for Tutorial

On 17.04.20 20:40, Erik Rijkers wrote: Very good stuff, and useful. I think. I mean that but nevertheless here is a lot of comment :) (I didn't fully compile as docs, just read the 'text' from the patch file) Thanks. Added nearly all of the suggestions. -- Jürgen Purtz d

Additional Chapter for Tutorial

he meanwhile its glossary-part is separated and commited. The new patch contains two elements: textual descriptions and 4 figures. My opinion concerning figures is set out in detail in the previous patch. Kind regards, Jürgen Purtz diff --git a/doc/src/sgml/advanced.sgml b/doc/src/sgml/advan

An XSLT example script

The example "XSLT Stylesheet for Converting SQL/XML Output to HTML" is tagged as , but it isn't a figure, it's an example script. The PDF output contains lists for examples, figures and tables and shows it in the wrong list. We should change the tagging. Jürgen P. diff --git a/doc/src/sgml/

Re: Getting our tables to render better in PDF output

it might get deprecated in future docbook versions. funcsynopsis, funcdef, function, ... keeps valid in Docbook 5, see: https://tdg.docbook.org/tdg/5.1/funcsynopsis.html . There is even an option to distinguish between K&R and ANSI style during rendering: Kind regards, Jürgen Purtz

Re: documentation pdf build fail (HEAD)

Ubuntu 18.04: no crash, but possibly a side effect: [INFO] FOUserAgent - Rendered page #2685. [INFO] FOUserAgent - Rendered page #2686. [INFO] FOUserAgent - Rendered page #2687. [WARN] FOUserAgent - Destination: Unresolved ID reference "function-encode" found. [WARN] FOUserAgent - Destination: U

Re: Shrinking SVG (Again)

So now we have two glossaries being proposed [1] [2], and they don't have much in common with each other. What to do now? If we can get the authors to agree on what patch to submit, we can move forward. I suggest to make a glossary be 0001, and then the other patches can be 0002 or further.

Re: Users/Roles do not align.

There's a few things wrong about this part anyway- namely that we've got FDWs now, and there's certainly other cluster-wide things that exist beyond the specific items listed, so I wonder if perhaps we should just stop trying to list everything here. Inspiring answer! After some inquiry I bec

Re: Users/Roles do not align.

Based on this, I believe Section 5.9 should read: `A PostgreSQL database cluster contains one or more named databases. Roles are shared across the entire cluster, but no other data is shared across databases. Any given client connection to the server can access only the data in a single database

Re: doc: Add anchors in create_table.sgml

We also converted from SGML to XML in the meantime, so you can probably make do with a standard XML parser without having to write a custom SGML one. Use XML tools with care! Some of our XML files are not well formed because they contain more than one root element. Kind regards, Jürgen Purtz.

Shrinking SVG (Again)

nal one is hard to read. Jürgen Purtz

Consolidation of first figures

attributes (fonts, sizes, colors) and structure for .gv files, changed texts in gin.gv, Makefile, README. Jürgen Purtz diff --git a/doc/src/sgml/geqo.sgml b/doc/src/sgml/geqo.sgml index 5120dfbb42..81cd84155a 100644 --- a/doc/src/sgml/geqo.sgml +++ b/doc/src/sgml/geqo.sgml @@ -84,59 +84,25

Re: Make 'Genetic Algorithm' a real figure

This is an adoption of the genetic-algorithm.gv file to the style of the gin.gv file: same font, similar header, use of TAB instead of SPACE. Kind regards Jürgen Purtz diff --git a/doc/src/sgml/geqo.sgml b/doc/src/sgml/geqo.sgml index 5120dfbb42..5a52fb46db 100644 --- a/doc/src/sgml

Re: Improvement of GIN figure

On Tue, Jul 9, 2019 at 3:22 PM Tatsuo Ishii wrote: I agree that the existing colors look awful, and that muted pastel colors would work better. Doesn't seem like something that should happen at the cost of making the diagram less informative, though. I am not an expert in the area but I think

Make 'Genetic Algorithm' a real figure

Currently the 'figure' of a genetic algorithm is created with some kind of 'ascii art'. The patch makes it a real figure. Kind regards Jürgen Purtz diff --git a/doc/src/sgml/geqo.sgml b/doc/src/sgml/geqo.sgml index 5120dfbb42..5a52fb46db 100644 --- a/doc/src/sgml/geq

Re: TOC: List of Figures

Peter Eisentraut writes: On 2019-07-02 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? If yes: The same for 'List of Tables' and 'List of Examples'? I

Improvement of GIN figure

To increase the consistency between the surrounding, explaining text and the figure, there are some changes and additions to the texts within the figure. Also: Added a hint in README for ditaa developers. Jürgen Purtz diff --git a/doc/src/sgml/images/README b/doc/src/sgml/images/README

Re: TOC: List of Figures

hem by default). The attached patch realizes the desired behavior. In 'func.sgml' there is also a modification because the given example isn't a figure, it's an example/programlisting. Jürgen Purtz diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 3a8581d205..538a9c

TOC: List of Figures

After the integration of figures into the documentation it may be helpful to extent the TOC with a 'List of Figures'. Any opinion? If yes: The same for 'List of Tables' and 'List of Examples'? There is a simple way to enable this feature: change line 56 of stylesheet-html-common.xsl to: "book

Re: graphviz file extension

On 24.05.19 09:08, 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 add more files in the future. +1 J. Purtz

Re: First SVG graphic

On 28.03.19 09:52, Peter Eisentraut wrote: On 2019-03-28 09:03, Tatsuo Ishii wrote: This has been committed. The SVG images are committed as well, so no new tools are required. What is the policy of adding graphics to PostgreSQL 12? Is it encouraged to add more graphics to 12 docs? Or do we wa

Re: First SVG graphic

2019. Kind regards Jürgen Purtz

Re: First SVG graphic

in the long lasting discussion, everybody shall use his favourite tool and deliver the original source plus a SVG version. Kind regards, Jürgen Purtz

Re: First SVG graphic

h a situation is low. Regarding comments, I believe tool-users will seldom use them. We can do without comments in the svg files of the repository. So find two files in the attachment: format (1): gin_Inkscape.svg and format (2): gin.svg. Kind regards, Jürgen Purtz

Re: First SVG graphic

On 08.03.19 18:55, Peter Eisentraut wrote: How do you get from the Inkscape SVG files to the what you call "optimized SVG" files? I loaded the gin_inkscape.svg file into Inkscape, saved it back out as "Plain SVG", but the resultant file did not look at all similar to the existing gin.svg. Inksc

Re: First SVG graphic

On 20.02.19 17:28, Peter Eisentraut wrote: On 2019-02-15 11:58, Jürgen Purtz wrote: The graphic for dump/restore is transferred from 'pg_dump utility' chapter to the 'backup and restore' chapter in sgml/backup.sgml. In this chapter I made a lot of textual changes to explain

Re: First SVG graphic

The graphic for dump/restore is transferred from 'pg_dump utility' chapter to the 'backup and restore' chapter in sgml/backup.sgml. In this chapter I made a lot of textual changes to explain the relation between pg_dump, pg_restore and psql in more detail. Especially I tried to introduce a more

Re: Tutorial section of documentation: enhancements needed

On 12.02.19 09:06, Lætitia Avrot wrote: I think we really need to take care of beginners who would like to install postgres on their laptop to "give it a try". +1

Re: First SVG graphic

On 07.02.19 12:06, Peter Eisentraut wrote: First, let's fix some of these whitespace errors: firstSvg_2.patch:677: trailing whitespace. Done. Let's not use mixed-case file names: Inkscape/ PageLayout.svg gin.svg pgDump.svg Done. @@ -152,15 +156,15 @@ postgres.txt: postgres.html post

Re: First SVG graphic

r PDF. * (In a future version there may also be a 'List of Program-Listings'. But this requires some more actions.) Kind regards, Jürgen Purtz diff --git a/doc/src/sgml/Makefile b/doc/src/sgml/Makefile index 8326c7c673..27d1e674f4 100644 --- a/doc/src/sgml/Makefile +++ b/doc/sr

Re: First SVG graphic

The attached patch contains all necessary changes to the sgml, svg, and Makefile. (Possibly we need some more changes regarding the 'install*' tasks of Makefile.) How to go on? Shall I send the patch to a different list or to Commitfest 2019-03? Kind regards Jürgen Purtz On 17.0

Re: First SVG graphic

? Or can we start to include the three first SVG graphics into PG's documentation? Kind regards Jürgen Purtz diff --git a/doc/src/sgml/stylesheet-html-nochunk.xsl b/doc/src/sgml/stylesheet-html-nochunk.xsl index ffd2012e91..3a20a47bce 100644 --- a/doc/src/sgml/stylesheet-html-nochu

Re: First SVG graphic

because Docbook 4.x is outdated since many years. Btw: Because of other problems (https://github.com/docbook/docbook/issues/74) it is likely that we cannot use 5.1 but have to wait for the upcoming release 5.2. Kind regards Jürgen Purtz

Re: First SVG graphic

a) The "Entry tree" and the "Posting trees" of the graphic "gin.svg" shows links not only from one tree-level to the next but also within each level from node to node. Is that correct? b) Is it worth to visualize PG's tree-implementation in a separate graphic - or is it the same as in every ot

Re: First SVG graphic

to three sgml files, which are necessary to incorporate the graphics. Kind regards Jürgen Purtz diff --git a/doc/src/sgml/Makefile b/doc/src/sgml/Makefile index 74aac01c39..2433571358 100644 --- a/doc/src/sgml/Makefile +++ b/doc/src/sgml/Makefile @@ -131,10 +131,12 @@ endif html: html-stamp

Re: First SVG graphic

es are online: https://wiki.postgresql.org/wiki/Category:SVG Kind regards Jürgen Purtz

Re: First SVG graphic

I take the reactions of the last days as a strong consent to go on with the effort to integrate graphics into the documentation and use SVG as the language which creates such graphics. Also the proposed parallel handling of two SVG files - a rich but tool-specific version (optional and not norm

Re: First SVG graphic

After one week no response at all? Neither positive nor negative. It seems that the community has little interest in the SVG issue. Or in my suggestion? Jürgen Purtz

Re: "System roles" mentioned in psql documentation

On 24.08.2018 02:21, Michael Paquier wrote: On Thu, Aug 23, 2018 at 10:53:35AM +0200, Jürgen Purtz wrote: This inconsistency is part of the more general problem that we miss a chapter, where our basic terms like 'database', 'cluster', 'segment', 'catalog

Re: "System roles" mentioned in psql documentation

This inconsistency is part of the more general problem that we miss a chapter, where our basic terms like 'database', 'cluster', 'segment', 'catalog', 'schema', ... are explicitly defined. Kind regards Jürgen Purtz

Re: Images in the official documentation

Because I strongly support the involvement of SVG into our documentation, I welcome every activity to establish this goal. The mail to which Pavel had replied (https://www.postgresql.org/message-id/4ea1bacb-02ca-e967-31d7-d2a6db30abff%40purtz.de) contained the two graphics /PageLayout.svg/ "Pag

Re: Images in the official documentation

On 19.07.2018 14:06, Pavel Golub wrote: I disagree. From what I heard, GraphViz is the winner for now. I can give you my two cents: plantuml is another good choice Ok, please give us an example - possibly the two previous graphics. Kind regards, Jürgen

Re: Appendix A. PostgreSQL Error Codes

I doubt that they are interested in the semantic order of subclass. But I do not know whether they prefer numeric to text or text to numeric translation. Jürgen Purtz On 27.04.2018 17:16, Tom Lane wrote: Bruce Momjian writes: On Fri, Apr 27, 2018 at 10:08:12AM +, PG Doc comments form wro

Re: Images in the official documentation

ins a very first draft as of Jan. 2016. Kind regards Jürgen Purtz On 23.02.2018 22:14, Daniel Westermann wrote: Hi %, I am working with PostgreSQL documentation quite a few years now and I am almost happy. What I think is completely missing (especially if you compare to commercial product doc