public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jürgen Purtz <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Erik Rijkers <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: Fabien COELHO <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Corey Huinker <[email protected]>
Cc: Justin Pryzby <[email protected]>
Cc: Roger Harkavy <[email protected]>
Cc: [email protected]
Cc: Michael Paquier <[email protected]>
Subject: Re: Add A Glossary
Date: Sun, 17 May 2020 10:09:48 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On 17.05.20 08:51, Alvaro Herrera wrote:
> Any object that
> exists in a database is local, regardless of whether it exists in a
> schema or not.
This implies that the term "local" is unnecessary, just call them "SQL 
object".
> "Extensions" is one type of object that does not belong
> in a schema.  "Foreign data wrapper" is another type of object that does
> not belong in a schema.  ...  They are*not*
> global objects.
postgres_fdw is a module among many others. It's only an example for 
"extensions" and has no different nature. Yes, they are not global SQL 
objects because they don't belong to the cluster.

In summary we have 3 types of objects: belonging to a schema, to a 
database, or to the cluster (global). Maybe, we can avoid the use of the 
different names 'local SQL object' and 'global SQL object' at all and 
just call them 'SQL object'. 'global SQL object' is used only once. We 
could rephrase "A set of databases and accompanying global SQL objects 
... " to "A set of databases and accompanying SQL objects, which exists 
at the cluster level, ... "

> TBH I'm not sure of this term at all.  I think we sometimes 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

view thread (97+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Add A Glossary
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox