Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jaLDr-0007co-TJ for pgsql-hackers@arkaria.postgresql.org; Sun, 17 May 2020 15:29:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jaLDp-0005MB-HI for pgsql-hackers@arkaria.postgresql.org; Sun, 17 May 2020 15:29:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jaLDp-0005M3-58 for pgsql-hackers@lists.postgresql.org; Sun, 17 May 2020 15:29:01 +0000 Received: from mail-qt1-x844.google.com ([2607:f8b0:4864:20::844]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jaLDk-0007i2-Hs for pgsql-hackers@postgresql.org; Sun, 17 May 2020 15:29:00 +0000 Received: by mail-qt1-x844.google.com with SMTP id a23so396265qto.1 for ; Sun, 17 May 2020 08:28:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=pU/z5LCTbBhZoRauHkcDlSDptaBOOvRvtNATfL5bAn4=; b=V7l7QH/rIVUg+Kt8bJHj7B6uhkvs7FfS+1E+g3VVpPSiPOaFGewhhfSHN1Za2CXrhT AHN7rngMyfYIU3O+lzykPg/ABzrCp8qg+vgU1xg50GE4/r3a1hEgRmHosmyTvtby4Fyt SQVX7PcNxZ7F9XaS6B2Jt6YFH/F+s+roUtF1kjpsRQ/u1e1JSrXUVHid7DRE8SufbMj4 MP+8/jqghZsXsECz4aHstYFknWxEbqmSFym9e8li5FFmOw9ocVe5eb16+XSY/XNgCixb TqzXEg4D9YcxCukD1U21QvBHAT3JlRVV+z0gomSQkZOO2Me+sekO1J21U8UUQzh/x53v 3K1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=pU/z5LCTbBhZoRauHkcDlSDptaBOOvRvtNATfL5bAn4=; b=ZifPdMqfnVrxUDGwhTRxxBiyMSLxPgoo5tbpnGmLN+PbFzo4EszFctrr5V22a/pjdE qYRCMD6YlzWswWWLGGDkSJWNwth7Jw1IqImA0PzroDsbDgPrCQz40Rb6/zkOOFWr7uzf p3fvGtaGUs7KqjolTP3HoXZoa7XVmaapx60BJTz7lQ1LU8hmhSSeFQ1o7ng92P/emtfQ GwCXxogly1LCYrFkIay+8dpFimdSVSQ1lmQFsVx06wPgfgDI5M7ukKzW3xbU8V+RiyTu B6E5OkgBAvSVc7RAR/23oPQSEOkeJ8z/j7hNKM4MdWE8Xy3o8NpIJMZuMaJLvxnkJFFW Zo3A== X-Gm-Message-State: AOAM530REFszJnnUEupXAJPzggYtMwglEoWmouKlgv7TVAyzTgs53xY+ /gM769Mn4GmV2/YuCGEATmr14Q== X-Google-Smtp-Source: ABdhPJzmSgKf5A/qtA2VT57uMkQsgSi8yLA/rF7YSwsKYDAmrqgXxNvuAHy4xAwo/K9q+9YaW63+EQ== X-Received: by 2002:ac8:38f2:: with SMTP id g47mr12337363qtc.118.1589729334762; Sun, 17 May 2020 08:28:54 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.95.18.252]) by smtp.gmail.com with ESMTPSA id x20sm7109166qtc.3.2020.05.17.08.28.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 17 May 2020 08:28:53 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 54B9A300710; Sun, 17 May 2020 11:28:51 -0400 (-04) Date: Sun, 17 May 2020 11:28:51 -0400 From: Alvaro Herrera To: Erik Rijkers Cc: =?iso-8859-1?Q?J=FCrgen?= Purtz , Laurenz Albe , Fabien COELHO , Peter Eisentraut , Corey Huinker , Justin Pryzby , Roger Harkavy , pgsql-hackers@postgresql.org, Michael Paquier Subject: Re: Add A Glossary Message-ID: <20200517152851.GA31376@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 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 never understood it that way, but I'm open to having my opinion on it changed. So let's discuss it and maybe gather opinions from others. I think the terms under discussion are just * cluster * instance * server We don't have "host" (I just made it a synonym for server), but perhaps we can add that too, if it's useful. It would be good to be consistent with historical Postgres usage, such as the initdb usage of "cluster" etc. Perhaps we should not only define what our use of each term is, but also explain how each term is used outside PostgreSQL and highlight the differences. (This would be particularly useful for "cluster" ISTM.) It seems difficult to get this sorted out before beta1, but there's still time before the glossary is released. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services