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 1t6kot-00FITh-5x for pgsql-general@arkaria.postgresql.org; Fri, 01 Nov 2024 06:07:39 +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 1t6kor-009pi2-4n for pgsql-general@arkaria.postgresql.org; Fri, 01 Nov 2024 06:07:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t6koq-009pet-Op for pgsql-general@lists.postgresql.org; Fri, 01 Nov 2024 06:07:37 +0000 Received: from mail-pj1-x102c.google.com ([2607:f8b0:4864:20::102c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t6koo-0048Fq-FP for pgsql-general@postgresql.org; Fri, 01 Nov 2024 06:07:36 +0000 Received: by mail-pj1-x102c.google.com with SMTP id 98e67ed59e1d1-2e2a97c2681so1250465a91.2 for ; Thu, 31 Oct 2024 23:07:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1730441252; x=1731046052; darn=postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=SHayUAoVhrOJ6h14aHHYlxcSifMhLeh+VEivZsiPrDI=; b=EfhxMDUn+PrfcY5XBQbJ64a3S69P6CWKnc1fgTfwzri4A9HTZd/6ScXxWr369sFAYM z/b/PN+auI0WkA2Ths5fueUuH3wt4BhVMnvyw6kBRq8J3TC6Ywqa9sG0bJjUdH5lBTxM HbjxiZTAkKxsY3wLvBz74w29OhtSS1bGYkrZ+LxY+lQ/SSyhSEKJzz4XXpG74PKM4Up8 lO/x0xI1olefraLdPqOrq1VOhH86AB5IvwF5MscPC9AUKVJcEQAOQAoLFsoje/KNnx/m B6C2oGOoeP/oWsM3vtLrs1nHcrJyG+JkE45STaJgXELap3t9k7lHSAWNM53kaWLcfR/w jkpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730441252; x=1731046052; h=content-transfer-encoding:cc: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=SHayUAoVhrOJ6h14aHHYlxcSifMhLeh+VEivZsiPrDI=; b=F3a79vRy41aOwho4y9zcFXmItdnVaJJGkiEJRyrieunddSas2Izjyarsmgdqy9l0Zk f51BJcou8Qi2xoGD/6rv0DiChBb/Ji7JBlhj73IG6KZNULFXfk3IJKswCqK7PEmw5xI+ EwSEjn0PTLc7VaDWn/3bI04rCBuOapr9Ey+ePisTeswcboqgztVIrKt+chdf9yNKmMTM 9zhknB7PBPk0ZmfAe7+lR5RFAg0RLD5iVZU6Te3vhhaPsYBy4Xj3UpuHqoB3ltXNH7Ut 8/9oqnQVdkXPR7I5rgD0Tao1TKsPN3Q293dBEe48JskPnz5gGIIr09VmaOXUCciYRVYX EEIQ== X-Gm-Message-State: AOJu0YyOubrnU62ibElGI2IhpcsVlWD/vzB/S78igL4Bvc/O+1zSCgce GnNdwWnHXvUniVJUgUGi0mHcut1+a+DftRKOGx8v1KX/g1e3QQQXIlCES0WaN7nC6IsXJiQdRC2 kHP3FNrOvkqbr4goLQ/2DOpY1r10IRsDr X-Google-Smtp-Source: AGHT+IErYeosE/ZQciko5sKXNFofaPoq5s0+qfYzh86zYQmSwsVDhbnpyqIOIzzp7QAw3DH8GsK1rhmhvlgmoQTH2RU= X-Received: by 2002:a17:90b:4c81:b0:2e0:f81c:731f with SMTP id 98e67ed59e1d1-2e92ce78860mr10367755a91.24.1730441251912; Thu, 31 Oct 2024 23:07:31 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ian Lawrence Barwick Date: Fri, 1 Nov 2024 15:07:20 +0900 Message-ID: Subject: Re: What to do with a PAAS-pg server To: "alexander al (leiden)" Cc: Postgres General Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 2024=E5=B9=B410=E6=9C=8831=E6=97=A5(=E6=9C=A8) 0:32 alexander al (leiden) <= alexander@scred.nl>: > > 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? If you mean you e.g. only have access to psql on the server in question, but want to know more about the server itself (i.e. not the PostgreSQL settings), then you might have luck poking around with the pg_read_file() function, e.g.: SELECT pg_read_file('/proc/meminfo'); Note you will need database superuser permission to execute pg_read_file(), or for non-superusers be granted EXECUTE permission on it. Regards Ian Barwick