Re: Add A Glossary - Mailing list pgsql-hackers

From Erik Rijkers
Subject Re: Add A Glossary
Date
Msg-id fcc01959cf90a5755819c50ae8005efa@xs4all.nl
Whole thread Raw
In response to Re: Add A Glossary  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Add A Glossary
List pgsql-hackers
On 2020-05-17 08:51, Alvaro Herrera wrote:
> On 2020-May-17, Jürgen Purtz wrote:
> 
>> On 15.05.20 02:00, Alvaro Herrera wrote:
>> > Thanks everybody.  I have compiled together all the suggestions and the
>> >
>> > * I changed "instance", and made "cluster" be mostly a synonym of that.
>> In my understanding, "instance" and "cluster" should be different 
>> things,
> 
> 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 them.  The instance is either running
> (in which case there are processes and RAM) or it isn't.

For what it's worth, I've also always understood 'instance' as 'a 
running database'.  I admit it might be a left-over from my oracle 
years:

   
https://docs.oracle.com/cd/E11882_01/server.112/e40540/startup.htm#CNCPT601

There, 'instance' clearly refers to a running database.  When that 
database is stopped, it ceases to be an instance.  I've always 
understood this to be the same for the PostgreSQL 'instance'.  Once 
stopped, it is no longer an instance, but it is, of course, still a 
cluster.

I know, we don't have to do the same as Oracle, but clearly it's going 
to be an ongoing source of misunderstanding if we define such a 
high-level term differently.

Erik Rijkers



pgsql-hackers by date:

Previous
From: Jürgen Purtz
Date:
Subject: Re: Add A Glossary
Next
From: Alexander Korotkov
Date:
Subject: Re: pgsql: Show opclass and opfamily related information in psql