On 2023-10-29 12:45:08 -0400, p...@pfortin.com wrote:
> On Sun, 29 Oct 2023 16:16:05 +0100 Peter J. Holzer wrote:
> >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;
>
On 10/29/23 09:45, p...@pfortin.com wrote:
On Sun, 29 Oct 2023 16:16:05 +0100 Peter J. Holzer wrote:
On 2023-10-29 09:21:46 -0400, p...@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
On 10/29/23 11:45, p...@pfortin.com wrote:
On Sun, 29 Oct 2023 16:16:05 +0100 Peter J. Holzer wrote:
On 2023-10-29 09:21:46 -0400, p...@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
On Sun, 29 Oct 2023 16:16:05 +0100 Peter J. Holzer wrote:
>On 2023-10-29 09:21:46 -0400, p...@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
On 2023-10-29 09:21:46 -0400, p...@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
On Sat, 28 Oct 2023 18:34:50 -0400 Jim Mlodgenski wrote:
Looking like a GOLD star for Jim...
>On Fri, Oct 27, 2023 at 7:46 PM wrote:
>
>> Memory: 125.5 GiB of RAM
>>
>It looks like you have a large amount of memory allocated to the server
>
>But your plans are doing reads instead of pulling
