On 03.04.21 21:01, Alvaro Herrera wrote:
On 2021-Apr-03, Jürgen Purtz wrote:
On 03.04.21 15:39, Alvaro Herrera wrote:
Yes, there is. AFAICS Heikki committed a small wordsmithing patch --
not the large patch with the additional chapter.
What can i do to move the matter forward?
Please post
On 03.04.21 15:39, Alvaro Herrera wrote:
Yes, there is. AFAICS Heikki committed a small wordsmithing patch --
not the large patch with the additional chapter.
What can i do to move the matter forward?
--
J. Purtz
On 15.03.21 03:47, Thomas Munro wrote:
On Thu, Mar 11, 2021 at 2:06 AM David Steele wrote:
On 12/1/20 3:38 AM, Jürgen Purtz wrote:
OK. Patch attached.
+Queries which access multiple tables (including repeats) at once are called
I'd write "Queries that" here (that's is a tra
On 18.01.21 15:13, Heikki Linnakangas wrote:
On 20/11/2020 23:52, Erik Rijkers wrote:
(smallish) Changes to arch-dev.sgml
This looks good to me. One little complaint:
@@ -125,7 +122,7 @@
use a supervisor process (also
master process) that spawns a new
server process every
? Initialized by
Heikki or by me?
--
Jürgen Purtz
On 30.11.20 21:25, David G. Johnston wrote:
Sorry, I managed to overlook the most recent patch.
I admitted my use of parentheses was incorrect and I don't see anyone
else defending them. Please remove them.
Minor typos:
"the database compare" -> needs an "s" (compares)
"In this case, the
On 30.11.20 20:45, Anastasia Lubennikova wrote:
As far as I see something got committed and now the discussion is stuck in
arguing about parenthesis.
FWIW, I think it is a matter of personal taste. Maybe we can compromise on
simply leaving this part unchanged.
With or without parenthesis is
On 02.11.20 07:15, Erik Rijkers wrote:
On 2020-11-01 16:38, Jürgen Purtz wrote:
On 30.10.20 17:45, Erik Rijkers wrote:
And I wrote down some separate items:
1.
'Two Phase Locking' and 'TPL' should be, I think,
'Two-Phase Commit'. Please someone confirm.
(no changes made)
Erik Rijkers
All
On 23.10.20 18:08, David G. Johnston wrote:
On Fri, Oct 23, 2020 at 3:18 AM Jürgen Purtz <mailto:juer...@purtz.de>> wrote:
and add a link to the "CREATE INDEX" command from the chapter
preamble.
is the link necessary?
I suppose it would make more sense to add
On 21.10.20 23:12, David G. Johnston wrote:
On Wed, Sep 30, 2020 at 4:25 AM Dagfinn Ilmari Mannsåker
mailto:ilm...@ilmari.org>> wrote:
Michael Paquier mailto:mich...@paquier.xyz>>
writes:
> On Mon, Aug 10, 2020 at 12:52:17PM +0000, Jürgen Purtz wrote:
&g
On 30.09.20 14:53, Heikki Linnakangas wrote:
On 30/09/2020 14:25, Dagfinn Ilmari Mannsåker wrote:
Michael Paquier writes:
On Mon, Aug 10, 2020 at 12:52:17PM +, Jürgen Purtz wrote:
The new status of this patch is: Waiting on Author
This has not been answered yet, so I have marked
The following review has been posted through the commitfest application:
make installcheck-world: not tested
Implements feature: not tested
Spec compliant: not tested
Documentation:tested, passed
a) I'm wondering if we should apply one more change to this page. The
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
;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
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
nding 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)
processes and RAM. (Here the term
"server" collides with new definitions in the glossary. But that's
another story.)
--
Jürgen Purtz
etimes use the
term "bloat" to talk about the dead rows only, ignoring the free space.
That's a good example for the necessity of the glossary. Currently we
don't have a common understanding about all of our used terms. The
glossary shall fix that and give a mandatory definition - after a
clearing discussion.
--
Jürgen Purtz
pe casts: Are you sure that they are global? In pg_cast
'relisshared' is 'false'.
--
Jürgen Purtz
diff --git a/doc/src/sgml/glossary.sgml b/doc/src/sgml/glossary.sgml
index 8bb1ea5d87..75f0dc9a8c 100644
--- a/doc/src/sgml/glossary.sgml
+++ b/doc/src/sgml/glossary.sgml
@@ -179,7 +179,7 @@
Bloat
On 11.04.20 21:47, Corey Huinker wrote:
Term 'relation': A sequence is internally a table with one row -
right?
Shall we extend the list of concrete relations by 'sequence'? Or
is this
not necessary because 'table' is already there?
I wrote one for sequence, it was a bit
On 2020-Apr-05, Jürgen Purtz wrote:
a) Some rearrangements of the sequence of terms to meet alphabetical order.
Thanks, will get this pushed.
b) --> in
two cases. Or should it be a ?
Ah, yeah, those should be linkend.
Term 'relation': A sequence is internally a table with one
a) Some rearrangements of the sequence of terms to meet alphabetical order.
b) -->
in two cases. Or should it be a ?
Kind regards, Jürgen
diff --git a/doc/src/sgml/glossary.sgml b/doc/src/sgml/glossary.sgml
index 8c6cb6e942..25762b7c3a 100644
--- a/doc/src/sgml/glossary.sgml
+++
- Server: is that really our definition?
I thought that "server" is what the glossary defines as "instance", and
the thing called "server" in the glossary should really be called "host".
Maybe I am too Unix-centered.
Many people I know use "instance" synonymous to "cluster".
+1 and many thanks to Alvaros edits.
Kind regards
Jürgen Purtz
On 31.03.20 19:58, Justin Pryzby wrote:
On Tue, Mar 31, 2020 at 04:13:00PM +0200, Jürgen Purtz wrote:
Please find some minor suggestions in the attachment. They are based on
Corey's last patch 0001-glossary-v4.patch.
@@ -220,7 +220,7 @@
Records to the file system and creates a special
On 31.03.20 20:07, Justin Pryzby wrote:
On Mon, Mar 30, 2020 at 01:10:19PM -0400, Corey Huinker wrote:
+
+Aggregating
+
+
+ The act of combining a collection of data (input) values into
+ a single output value, which may not be of the same type as the
+ input
On 30.03.20 19:10, Corey Huinker wrote:
On Sun, Mar 29, 2020 at 5:29 AM Jürgen Purtz <mailto:juer...@purtz.de>> wrote:
On 27.03.20 21:12, Justin Pryzby wrote:
> On Fri, Mar 20, 2020 at 11:32:25PM +0100, Jürgen Purtz wrote:
>>>> + Archiver
>>>
On 27.03.20 21:12, Justin Pryzby wrote:
On Fri, Mar 20, 2020 at 11:32:25PM +0100, Jürgen Purtz wrote:
+Archiver
Can you change that to archiver process ?
I prefer the short term without the addition of 'process' - concerning
'Archiver' as well as the other cases. But I'm not an native
On 24.03.20 19:46, Robert Haas wrote:
Do we use shared_buffers for WAL ?
No.
What's about the explanation in
https://www.postgresql.org/docs/12/runtime-config-wal.html :
"wal_buffers (integer) The amount of shared memory used for WAL data
that has not yet been written to disk. The
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:
On 21.03.20 00:03, Justin Pryzby wrote:
+
+Host
+
+
+ See Server.
Or client. Or proxy at some layer or other intermediate thing. Maybe just
remove this.
Sometimes the term "host" is used in a different meaning. Therefor we shall
have this glossary entry for clarification
On 20.03.20 20:58, Justin Pryzby wrote:
On Thu, Mar 19, 2020 at 09:11:22PM -0300, Alvaro Herrera wrote:
+Aggregate
+
+
+ To combine a collection of data values into a single value, whose
+ value may not be of the same type as the original values.
+ Aggregate
man pages: Sorry, if I confused someone with my poor English. I just
want to express in my 'offline' mail that we don't have to worry about
man page generation. The patch doesn't affect files in the /ref
subdirectory from where man pages are created.
review process: Yes, it will be
The statement that names of schema objects are unique isn't
/strictly/ true, just /mostly/ true. Take the case of a unique
constraints.
Concerning CONSTRAINTS you are right. Constraints seems to be an exception:
* Their name belongs to a schema, but are not necessarily unique
within
I made changes on top of 0001-add-glossary-page.patch which was supplied
by C. Huinker. This affects not only terms proposed by me but also his
original terms. If my changes are not obvious, please let me know and I
will describe my motivation.
Please note especially lines marked with
On 16.08.19 23:00, Alvaro Herrera wrote:
On 2019-Mar-27, Peter Eisentraut wrote:
doc: Add some images
Add infrastructure for having images in the documentation, in SVG
format. Add two images to start with. See the included README file
for instructions.
Author: Jürgen Purtz
Author: Peter
36 matches
Mail list logo
