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 1rebKk-00CHLx-DR for pgsql-novice@arkaria.postgresql.org; Mon, 26 Feb 2024 13:47:54 +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 1rebKj-00DhrE-1v for pgsql-novice@arkaria.postgresql.org; Mon, 26 Feb 2024 13:47:53 +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 1rebKi-00Dhr4-Pp for pgsql-novice@lists.postgresql.org; Mon, 26 Feb 2024 13:47:53 +0000 Received: from mail-oa1-x32.google.com ([2001:4860:4864:20::32]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rebKf-001CnN-E4 for pgsql-novice@lists.postgresql.org; Mon, 26 Feb 2024 13:47:52 +0000 Received: by mail-oa1-x32.google.com with SMTP id 586e51a60fabf-21e5fa2f7efso1440961fac.0 for ; Mon, 26 Feb 2024 05:47:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708955270; x=1709560070; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=PCIPpcpgcnPKJfJkfdPfwVMTfIokAF+1vy5XZvJZ56U=; b=Lbq0gIawY65SHeoIR3NcmNXhZ4RslxaVlLuWbooBZN5S9lXdRsTaEZkJ/D54peJIp+ ldDuxpvSjXIWtS60U20KFKALRtiVw4phopU9LdxE9ptkwk9a4/MzowBVidCC3Y3a3wnF 8yVlVQ25c91d2KY4eWZrxvgdWpMQEw9wqem1F9L/rMprYvY/uQvFluO1h/SrPsIDmVlT 9mLwK1ci4tiKhQIL8Q3zQhquTwD6eKw21ecOXUysTVL7k3xyKLJVLJ7XDwOtCMHa+16N rhynWQY5WoZ+2UE5dfMOZWIck0fS7x6hAlnAv5rlJm0XCZqVLYeSI94jiJYl0eLSXeqb ZGAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708955270; x=1709560070; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=PCIPpcpgcnPKJfJkfdPfwVMTfIokAF+1vy5XZvJZ56U=; b=ZvuIR5I/bIyfHMvsMuLBsAFYZdYM7Z5QESsvXDSEkqgCg6DjT8Gai6RtB1p2CTRi7y 395AW/I6UV540Xzz3Fpg+pJosuFoJadFEQgyrv+1zuIOnvqZ/35C2bnKeANYl7eZBLRo g8lPpHYS9oqAVhlAzM+mQFv9W4P99MkPSTZOJYSZWLC+kl2lZssRbj6Q8snB1+slM/T1 IfjTe0U6fnM5b5npdQW8vI4YKFJn6aTH3v9UvY8uXFt2eNcqNtnvvimGTDXXpZW9qRHV 5Jazrf+7Mkhjlvd79cNSd7fzONaIEzxgTR3N+0DuHcRWI9FM2neRlnU0nGSLXoscAuk4 EHEA== X-Gm-Message-State: AOJu0YwUKNX1WBv7CQ2NVrvm9oD1VxE6IBzS6wkRyOa1FM7PDDLk9A+s pxAB/COtfye8DBX/290L5lBc8TstinQ5lOdkGaEiHHyPqFafCfXzhCfS0JCnX798U/LaQ2rQrhX 0kKgOwWGzoo0yFoUlfQzdTEUlXuYdKUyf4Vk= X-Google-Smtp-Source: AGHT+IHE+BoOplSD29dqUMDR1SNIPzWtlGoDJCcXQ4Gdz3Pqa/xkaVHLIa+fzJYJJokXzKg7amp3pZYUjXuMWUseeMY= X-Received: by 2002:a05:6870:9d13:b0:21e:6320:ba05 with SMTP id pp19-20020a0568709d1300b0021e6320ba05mr6584599oab.23.1708955269602; Mon, 26 Feb 2024 05:47:49 -0800 (PST) MIME-Version: 1.0 From: blockdump Date: Mon, 26 Feb 2024 14:47:38 +0100 Message-ID: Subject: Reset date for Cumulative Statistics System when not in table To: pgsql-novice@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000c821ee0612492735" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c821ee0612492735 Content-Type: text/plain; charset="UTF-8" Hello, I am new to Postgres and started reading about the The Cumulative Statistics System. https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STATIO-ALL-TABLES-VIEW When I came across pg_statio_all_tables I was wondering what is the reference date for the counters like (heap_blks_read, heap_blks_hit ... ) This table does not have a stats_reset column like others. So are this numbers accumulating from the creation of the table or since the startup of the cluster ? Maybe someone can drop me a line. cheers Guenter --000000000000c821ee0612492735 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,=C2=A0
I am new to Postgres and started reading = about the=C2=A0The Cumulative Statistics System.=C2=A0

<= div>When I came across pg_statio_all_tables I was wondering what is the ref= erence date for the counters like (heap_blks_read,=C2=A0heap_blks_hit ... )= This table does not have a=C2=A0stats_reset column like others.=C2=A0
So are this numbers accumulating from the creation of th= e table or since the startup of the cluster=C2=A0?

Maybe someone can drop me a line.

cheers
Guenter=C2=A0 --000000000000c821ee0612492735--