pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: pf@pfortin.com
To: pgsql-general@lists.postgresql.org
Subject: Re: [SOLVED?] Re: Disk wait problem...  not hardware...
Date: Sun, 29 Oct 2023 12:45:08 -0400
Message-ID: <20231029124508.71a8ce22.pfortin@pfortin.com> (raw)
In-Reply-To: <20231029151605.kijo6gumeen7jj26@hjp.at>
References: <fe8042a8-5747-466e-ac8a-de3c5b6a469c@aklaver.com>
	<20231023175529.59f309bb@pfortin.com>
	<9938ff1a-8837-454b-a50c-a748e84c172a@aklaver.com>
	<20231026095000.4swq6vbgdsw3palp@hjp.at>
	<20231026155016.6b739a7e.pfortin@pfortin.com>
	<20231026220325.2204a3f6.pfortin@pfortin.com>
	<20231027170711.xgz3xrf7cujx7udh@hjp.at>
	<20231027194609.1bf96324.pfortin@pfortin.com>
	<CAB_5SRd_z8eL-uypDTRVBNweJio_p9+M3RgkbWyO5zt4MB0Hvg@mail.gmail.com>
	<20231029092146.53351f7e@pfortin.com>
	<20231029151605.kijo6gumeen7jj26@hjp.at>

On Sun, 29 Oct 2023 16:16:05 +0100 Peter J. Holzer wrote:

>On 2023-10-29 09:21:46 -0400, pf@pfortin.com wrote:
>> These are all static tables. Does PG maintain a table row count so as to
>> avoid having to count each time?  
>
>No. To count the rows in a table, Postgres has to actually read the
>whole table (or an index, if a suitable index (e.g. a primary key)
>exists).

Am I correct to assume count(fieldname) would only load that column for
counting?  In other words: we should be specific (avoid "*") in general?

>However, the table statistics contain an estimate for the number of
>rows:
>
>hjp=> select schemaname, relname, n_live_tup from pg_stat_user_tables order by 3 desc;  
>╔════════════╤═══════════════════════════╤════════════╗
>║ schemaname │          relname          │ n_live_tup ║
>╟────────────┼───────────────────────────┼────────────╢
>║ public     │ ncvhis_2016_12_03         │    9999977 ║
>║ public     │ random_test               │    1000000 ║
>║ public     │ beislindex                │        351 ║
>║ public     │ delivery                  │          6 ║
>...

Are there prerequisites for this query?
Every (264) n_live_tup returned was zero...  though, VERY fast.. :)

>This is an estimate, not the actual count, so it might be wrong
>(sometimes very wrong), but accessing it is fast and it might be good
>enough for your purposes.

Thanks for sharing...  We're learning fast... :)

>> WB is setup to:
>> * autoload table row count
>> * autoload table data (restricted with LIMIT)  
>
>Maybe WB can be set up to get n_live_tup instead of the real row count?

It appears this is hard-coded [on/off only]; but I thought I saw the WB
author post on this list recently...

>        hp
>





view thread (6+ messages)  latest in thread

Message-ID: <20231029124508.71a8ce22.pfortin@pfortin.com>
Permalink:  ../20231029124508.71a8ce22.pfortin@pfortin.com/
Also on:    postgresql.org/message-id/20231029124508.71a8ce22.pfortin@pfortin.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: pf@pfortin.com
  Subject: Re: [SOLVED?] Re: Disk wait problem...  not hardware...
  In-Reply-To: <20231029124508.71a8ce22.pfortin@pfortin.com>
  References: <fe8042a8-5747-466e-ac8a-de3c5b6a469c@aklaver.com> <20231023175529.59f309bb@pfortin.com> <9938ff1a-8837-454b-a50c-a748e84c172a@aklaver.com> <20231026095000.4swq6vbgdsw3palp@hjp.at> <20231026155016.6b739a7e.pfortin@pfortin.com> <20231026220325.2204a3f6.pfortin@pfortin.com> <20231027170711.xgz3xrf7cujx7udh@hjp.at> <20231027194609.1bf96324.pfortin@pfortin.com> <CAB_5SRd_z8eL-uypDTRVBNweJio_p9+M3RgkbWyO5zt4MB0Hvg@mail.gmail.com> <20231029092146.53351f7e@pfortin.com> <20231029151605.kijo6gumeen7jj26@hjp.at> <20231029124508.71a8ce22.pfortin@pfortin.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox