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 1s0icM-006lEm-Te for pgsql-general@arkaria.postgresql.org; Sat, 27 Apr 2024 14:01:30 +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 1s0icK-0075Sw-By for pgsql-general@arkaria.postgresql.org; Sat, 27 Apr 2024 14:01:29 +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 1s0icJ-0075NG-0D for pgsql-general@lists.postgresql.org; Sat, 27 Apr 2024 14:01:27 +0000 Received: from mail-oo1-xc2e.google.com ([2607:f8b0:4864:20::c2e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s0icH-000JAQ-5g for pgsql-general@lists.postgresql.org; Sat, 27 Apr 2024 14:01:26 +0000 Received: by mail-oo1-xc2e.google.com with SMTP id 006d021491bc7-5aa1b7a37b5so1855732eaf.2 for ; Sat, 27 Apr 2024 07:01:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714226484; x=1714831284; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=LNZt8hRzXBUW+aB0BuTSkRv/OIwZdDGGz09iOn2Mqok=; b=KDLmhXHnuZ47FLM4QJrxCxYIl5byQ2f94WdYbsKiaXKevmv/IS+5KA8VzP9IfjzhgX YReHSFVkK5pcRvA+b0dox3YGFP7ZHB0LsW7CaJsquuPNrar51zMk8JQn4hJ7FGrxdSvv 87SHeGo1h3tOqcOqFoA9wuwgOG2P9oPhADDrDgM/7H1XxSTkJbJaZPKuH9L/7WJySeuG 6sbjbVjveYgSbngWwC9RL9QlWihNyCsH8LWvn8mJ9ZdBE+1dWPi0wgkNUqD88+sGFHP0 LH0VF74yd0MMa6K+bPDpqCJev4x1618mBtccwJXJkzICHKMOzb/Kxl+V4Erh42s3UCke sXgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714226484; x=1714831284; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=LNZt8hRzXBUW+aB0BuTSkRv/OIwZdDGGz09iOn2Mqok=; b=NpCwgX8HpmMPkYg35ZokPMhpeZvETselu2me1GtcXPeds+0OMePqZ0fXXa/bZ5kxX9 Fk0F2aZiNy2FB3YNctMyizFiYnGLu4rTZN4V7uk3UIeLGkNMpo0bSxGTFpEw30mF0iua SoIcaeMhWttMyqn9sKwbAyJ0qHd0UFGxn6lp/Fhx9Md3MoP3RfTPRcOW1ebHifiQLI0W Uk8byxTjvguDFoD9BJMnLDQ5fpXKNRA5yIZBtdlD3X13gSJyy44VwXJnCsPl+0SPQtsR 6hJfin6iwTtaMJ7iyKW4I2COl9hz7QbZmIUIl5aUAH0TVWBAyY9E4cVlbPjpgALsL9tN of8g== X-Gm-Message-State: AOJu0YyHhtytckQTvM/f5afRCfNwloQWsPs9uwGMNBL+tt9AKYAUuj03 eyDE4+bzgwBuv5/0vYUvSp0hEkPXaXsvPRUT2ZJHlBt9HiCIT3RQUU2GynYDSFwfQ1ZayePjQOp xM3MBqXrh4MJeIqkKNyJsRPrnIcFqbRi4 X-Google-Smtp-Source: AGHT+IFWpAO1Cd6Ngyc3lNXRamJQJTJTFvD6ZI2ugWLgHBnTh4+pTg0VidorGAGZTaByfbokMoJIMW3eKPdIhYpZQdg= X-Received: by 2002:a05:6358:d587:b0:18a:e9ac:bdf1 with SMTP id ms7-20020a056358d58700b0018ae9acbdf1mr4860259rwb.17.1714226484246; Sat, 27 Apr 2024 07:01:24 -0700 (PDT) MIME-Version: 1.0 From: sud Date: Sat, 27 Apr 2024 19:31:12 +0530 Message-ID: Subject: Monitoring and debugging historical performance To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000a87fe3061714742c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a87fe3061714742c Content-Type: text/plain; charset="UTF-8" Hi All, While looking option to see how one can monitor database performance for debugging into historical database performance issues (historical database wait events , CPU/memory utilization in past, query execution times in past , executions paths at any point in time in past etc), It appears there exists some options as i googled in the internet like pg_sentinel,pgsnapper, pg_collector. Wanted to check, if anybody used these utilities and suggest any of them to use for a longer term use? Regards Sud --000000000000a87fe3061714742c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,
While looking option to see how one can monitor= database performance for debugging into historical database performance is= sues (historical database wait events , CPU/memory utilization in past, que= ry execution times in past , executions paths at any point in time in past = etc), It appears there exists some options as i googled in the internet lik= e pg_sentinel,pgsnapper, pg_collector. Wanted to check, if anybody used the= se utilities and suggest any of them to use for a longer term use?
=
Regards
Sud
--000000000000a87fe3061714742c--