Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t6Ax9-00B9xb-LO for pgsql-general@arkaria.postgresql.org; Wed, 30 Oct 2024 15:49:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t6Ax7-00AGcW-73 for pgsql-general@arkaria.postgresql.org; Wed, 30 Oct 2024 15:49:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t6Ax6-00AGcO-PL for pgsql-general@lists.postgresql.org; Wed, 30 Oct 2024 15:49:45 +0000 Received: from mail-oo1-xc2c.google.com ([2607:f8b0:4864:20::c2c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t6Ax4-003e5k-IU for pgsql-general@postgresql.org; Wed, 30 Oct 2024 15:49:43 +0000 Received: by mail-oo1-xc2c.google.com with SMTP id 006d021491bc7-5ebc9bda8c8so29701eaf.0 for ; Wed, 30 Oct 2024 08:49:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1730303381; x=1730908181; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=/v7kS8WJ3vXzJBK6+eDPEx4bb4vaT/a8XvzyqL8mbR8=; b=dTGuRgeKp4UGzorokRZM0JgCFpTOX8NXE2Ke4uNdj69v4NRifP2T+QN0UxEvabstnL YjfEpVnXEDASkCs9E6oPk4WF1WObqzCpvBGj+6PBGcH4p0DpW69X52SiqIV7RcF/wXlx 9aoDxEvlAY1z7LbBHlmUVzvl96HX3azBy9klhS5RfEuSR4YPxkbFh7j3AG8PccHcp5ry CkGwumPrHHC9Y10GuEt7AWJ7MiL+EDgW2WaKntFiMrFuBrU47xaeMIOGa+Q1c1EzCuZI fA50Jx09LFBswTYDX/Bn95OQeEg/0Ge+kuKf4PjfsDW8QngA+rtfhxfxfnwQVlXVkje1 k9ig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730303381; x=1730908181; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=/v7kS8WJ3vXzJBK6+eDPEx4bb4vaT/a8XvzyqL8mbR8=; b=XWes97fATGPVxjD9A68U087iSO5+bIQLw6LwxJE3AV8K/WKASsro0QQ8YaX9czDDh2 +96tux2wlw8rAcuU+sIUFejF72zVfsAU169WsrAkRWI6tuQgfzE8fneACF9iewYLBvdY XTwJMdfWFy4o/rgxnO/x6g6bU+da5eIS2QmxfwtFC9PvuArnLa6BNWzwADduGj3gYxPt rDV/dpFdc60ptPuFwPO8Ebi5HgHafrnQkwerJyF2UhRFnLqlYn+yAz8s6PQSStmhyaE8 mwK1HMwMpHxHZjgA3R9tN77yRDJNehcxMMfb05JEuegwU4pZBMKCybUygivEOXnk0dMs Lyfw== X-Gm-Message-State: AOJu0YzcjC1iVGwGB+hMIRhSQWyUvexv1qNj2k+j4QIbIp+OTZ5oEqe8 BW3ey2G3zGfbt3stsbnTDg900a4N7OWUah4MBJc+80Q//ta4J4/iaURCKi8Sgi/62AuJ5WqltRG STZnuFsxLK7AXL7vIosiTpOYffQClMw== X-Google-Smtp-Source: AGHT+IH2NfbYC8lfcQMM9cWTk5Xrr0M1V7erX5SoGNdTWrYqQX1F4TNUgo4iuAlk6i4V8lYDKijw6gh4oDHgcJvgpo0= X-Received: by 2002:a05:6820:1e02:b0:5e1:ea03:928f with SMTP id 006d021491bc7-5ec23a6e68fmr9878544eaf.7.1730303381056; Wed, 30 Oct 2024 08:49:41 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Wed, 30 Oct 2024 11:49:29 -0400 Message-ID: Subject: Re: What to do with a PAAS-pg server To: pgsql-general Content-Type: multipart/alternative; boundary="00000000000061b7840625b3a6f4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000061b7840625b3a6f4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Settings, like "SELECT * FROM pg_settings;" On Wed, Oct 30, 2024 at 11:32=E2=80=AFAM alexander al (leiden) wrote: > Hi, > > we have a supplier (via our client) who has an self build PAAS-version > of postgresql. Ok, you would say, that's fine. But, there is always an > but, we think the settings are not quite ok. We really want to know how > much memory etc there is on that server. So we can recommend the > recommended settings. Is there a way to get those information on the > server itself from psql? > > regards, > > Alexander Al > > > > > --=20 Death to , and butter sauce. Don't boil me, I'm still alive. crustacean! --00000000000061b7840625b3a6f4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Settings, like "SELECT * FROM pg_set= tings;"

On Wed, Oct 30, 2024 at 11:32=E2=80=AFAM alexander al (leiden) = <alexander@scred.nl> wrote:=
Hi,

we have a supplier (via our client) who has an self build PAAS-version
of postgresql. Ok, you would say, that's fine. But, there is always an<= br> but, we think the settings are not quite ok. We really want to know how
much memory etc there is on that server. So we can recommend the
recommended settings. Is there a way to get those information on the
server itself from psql?

regards,

Alexander Al






--
Death to <Redacted>, and butter sauce.
Don't b= oil me, I'm still alive.
<Redacted> crustacean!
--00000000000061b7840625b3a6f4--