On 2024-04-25 22:00 +0200, Alexander Lakhin wrote:
> 25.04.2024 12: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
Hello,
25.04.2024 12: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 P
On 2024-Apr-25, Jürgen Purtz wrote:
> Great recommendation. I may have time in the second half of June to
> pursue the migration further. There is a performance problem, which
> possibly results from our XSLT script that optimizes the
> transformation-speed and works well in 4.x.
Maybe a way to
On 2024-04-25 15:40 +0200, Jürgen Purtz wrote:
> 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 (l
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 with the mi
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 Purtz p
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 Purtz proposed.
https://postgr.es/m/21ed3fd9-90
On 2024-04-12 18:29 +0200, Anton Voloshin wrote:
> In REL_13_STABLE and above, generated HTML have a broken HTML: nested href="..."> tags for all links to glossary. Somehow, this results in
> duplicated tags on the https://www.postgresql.org/docs/
>
> Foun
Hello,
In REL_13_STABLE and above, generated HTML have a broken HTML: nested href="..."> tags for all links to glossary. Somehow, this results in
duplicated tags on the https://www.postgresql.org/docs/
Found by tab-navigating https://www.postgresql.org/docs/16/rowtypes.html
On 02.05.23 12:55, Daniel Gustafsson wrote:
On 2 May 2023, at 12:24, Alvaro Herrera wrote:
On 2023-May-02, Daniel Gustafsson wrote:
+
+ LSN
+
+
The other entries doesn't have a glossentry id
attribute set, is the use here related to the glossentry.show.acronym param?
I debated wi
> On 2 May 2023, at 12:24, Alvaro Herrera wrote:
>
> On 2023-May-02, Daniel Gustafsson wrote:
>
>> +
>> + LSN
>> +
>> +
>>
>> The other entries doesn't have a glossentry id
>> attribute set, is the use here related to the glossentry.show.acronym param?
>
> I debated with myself for 3
On 2023-May-02, Daniel Gustafsson wrote:
> +
> + LSN
> +
> +
>
> The other entries doesn't have a glossentry id
> attribute set, is the use here related to the glossentry.show.acronym param?
I debated with myself for 347d2b07fcc2 on whether to add id attribs to
entries. The only savi
> On 2 May 2023, at 09:05, Peter Eisentraut
> wrote:
>
> I wrote glossary entries for some terms I wanted to look up there but didn't
> find: "restartpoint" and "LSN". I put this together based on existing text.
> "LSN" was already in t
I wrote glossary entries for some terms I wanted to look up there but
didn't find: "restartpoint" and "LSN". I put this together based on
existing text. "LSN" was already in the acronyms list but I think it's
more appropriate in the gloss
On 2022/01/08 1:41, Tom Lane wrote:
Fujii Masao writes:
In glossary, the title of each term about process seems to consist of the process name and
"(process)", e.g., Checkpointer (process). But I found that "(process)" is missing for
the following three terms about
Fujii Masao writes:
> In glossary, the title of each term about process seems to consist of the
> process name and "(process)", e.g., Checkpointer (process). But I found that
> "(process)" is missing for the following three terms about process. Attached
> is
Hi,
In glossary, the title of each term about process seems to consist of the process name and
"(process)", e.g., Checkpointer (process). But I found that "(process)" is missing for
the following three terms about process. Attached is the patch to add "(process)"
On 2020-Jul-21, Jürgen Purtz wrote:
> - Added '(process)' to the two terms 'Autovacuum' and 'Stats Collector'
>
> - Removed link to himself in 'Logger (process)'
>
> - new term: Base Backup
Pushed. I was not courageous enough to include "base backup" in 13, so
that one's in master only, but th
On 19.06.20 19:10, Alvaro Herrera wrote:
Thanks for these fixes! I included all of these.
On 2020-Jun-19, Erik Rijkers wrote:
And one thing that I am not sure of (but strikes me as a bit odd):
there are several cases of
'are enforced unique'. Should that not be
'are enforced to be unique' ?
Thanks for these fixes! I included all of these.
On 2020-Jun-19, Erik Rijkers wrote:
> And one thing that I am not sure of (but strikes me as a bit odd):
> there are several cases of
> 'are enforced unique'. Should that not be
> 'are enforced to be unique' ?
I included this change too; I am no
On 2020-06-19 01:51, Alvaro Herrera wrote:
On 2020-Jun-16, Justin Pryzby wrote:
On Tue, Jun 16, 2020 at 08:09:26PM -0400, Alvaro Herrera wrote:
I noticed one typo:
'aggregates functions' should be
'aggregate functions'
And one thing that I am not sure of (but strikes me as a bit odd):
ther
t;/\1/' > orig
LC_COLLATE=en_US.UTF-8 sort orig > sorted
(Eliminating the tags is important, otherwise the sort uses the tags
themselves to disambiguate)
> One last question: The definition of "Data directory" reads "... A cluster's
> storage space comprises the da
ry" reads "... A
cluster's storage space comprises the data directory plus ..." and
'cluster' links to '"glossary-instance". Shouldn't it link to
"glossary-db-cluster"?
--
Jürgen Purtz
diff --git a/doc/src/sgml/glossary.sgml b/doc
> The base directory on the filesystem of a
> server that contains
> all
> - data files and subdirectories associated with an
> - instance (with the
> - exception of linkend="glossary-tablespace">tablespaces).
> + data files and subdi
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: "Tables are grouped into
> databases, and a collection of dat
On 17.05.20 17:28, Alvaro Herrera wrote:
I think the terms under discussion are just
* cluster
* instance
* server
Despite the short period of its existence the glossary achieved some
importance, see:
https://www.postgresql.org/message-id/b8e12875ebec9e6d3107df5fa1129e1e%40postgrespro.ru
On Wed, 2020-05-20 at 13:17 +0200, Jürgen Purtz wrote:
> > FWIW, I feel somewhat like Alvaro on that point; I use those terms
> > synonymously,
> > perhaps distinguishing between a "started cluster" and a "stopped cluster".
> > After all, "cluster" refers to "a cluster of databases", which are the
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 no
On 2020-05-19 08:17, Laurenz Albe wrote:
The term "cluster" is unfortunate, because to most people it suggests a group of
machines, so the term "instance" is better, but that ship has sailed long ago.
I don't see what would stop us from renaming some things, with some care.
--
Peter Eisentraut
I think there needs to be a careful analysis of the language and a formal
effort to stabilise it for the future.
In the context of, say, an Oracle T series, which is partitioned into
multiple domains (virtual machines) in it, each
of these has multiple CPUs, and can run an instance of the OS which
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 not at all. They use a common
> initia
On 17.05.20 17:28, Alvaro Herrera wrote:
On 2020-May-17, Erik Rijkers wrote:
On 2020-05-17 08:51, Alvaro Herrera wrote:
I don't think that's the general understanding of those terms. For all
I know, they*are* synonyms, and there's no specific term for "the
fluctuating objects" as you call th
On Thu, 2020-01-02 at 21:24 +, PG Doc comments form wrote:
> Page: https://www.postgresql.org/docs/12/creating-cluster.html
> Description:
>
> It would be great to have a glossary as an appendix, to define concepts such
> as cluster, schema, tablespace, database.
Does the in
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/creating-cluster.html
Description:
It would be great to have a glossary as an appendix, to define concepts such
as cluster, schema, tablespace, database.
34 matches
Mail list logo
