Re: Disk wait problem... may not be hardware...

2023-10-29 Thread pf
On Sun, 29 Oct 2023 16:00:46 +0100 Peter J. Holzer wrote: >On 2023-10-27 19:46:09 -0400, p...@pfortin.com wrote: >> On Fri, 27 Oct 2023 19:07:11 +0200 Peter J. Holzer wrote: >> >Have you looked at the query plans as I recommended? (You might also >> >want to enable track_io_timing to get extra

Re: Disk wait problem... may not be hardware...

2023-10-29 Thread Peter J. Holzer
On 2023-10-27 19:46:09 -0400, p...@pfortin.com wrote: > On Fri, 27 Oct 2023 19:07:11 +0200 Peter J. Holzer wrote: > >Have you looked at the query plans as I recommended? (You might also > >want to enable track_io_timing to get extra information, but comparing > >just the query plans of fast and

Re: Disk wait problem... may not be hardware...

2023-10-28 Thread Jim Mlodgenski
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 things from shared buffers >explain (analyze, buffers) select count(*) from ncvhis_2016_12_03; >

Re: Disk wait problem... may not be hardware...

2023-10-28 Thread pf
On Fri, 27 Oct 2023 21:21:18 -0700 Adrian Klaver wrote: >On 10/27/23 16:46, p...@pfortin.com wrote: >> Peter, >> >> Thanks for your patience; I've been feeling pressure to get this >> resolved; so have been lax in providing info here.. Hope the following >> helps... >> > > >> Something I

Re: Disk wait problem... may not be hardware...

2023-10-27 Thread Adrian Klaver
On 10/27/23 16:46, p...@pfortin.com wrote: Peter, Thanks for your patience; I've been feeling pressure to get this resolved; so have been lax in providing info here.. Hope the following helps... Something I hadn't noticed before: SQL-workbench/J (build 129.6) displays an execution timer

Re: Disk wait problem... may not be hardware...

2023-10-27 Thread pf
Peter, Thanks for your patience; I've been feeling pressure to get this resolved; so have been lax in providing info here.. Hope the following helps... On Fri, 27 Oct 2023 19:07:11 +0200 Peter J. Holzer wrote: >On 2023-10-26 22:03:25 -0400, p...@pfortin.com wrote: >> Are there any extra PG

Re: Disk wait problem... may not be hardware...

2023-10-27 Thread Peter J. Holzer
On 2023-10-26 22:03:25 -0400, p...@pfortin.com wrote: > Are there any extra PG low level logs that can be turned on? Have you looked at the query plans as I recommended? (You might also want to enable track_io_timing to get extra information, but comparing just the query plans of fast and slow

Re: Disk wait problem... may not be hardware...

2023-10-27 Thread Justin Clift
On 2023-10-27 12:03, p...@pfortin.com wrote: I can't think of a common hardware bus/other that would only affect PostgreSQL disk accesses. Which file system is PostgreSQL being run on? Asking because I remember seeing weirdness reported with *some* SSD drives when used with ZFS:

Re: Disk wait problem... may not be hardware...

2023-10-26 Thread pf
On Thu, 26 Oct 2023 15:50:16 -0400 p...@pfortin.com wrote: >Hi Peter, > >All of the following is based on using SQL_workbench/J (WB) (Mageia Linux >has not provided a viable pgAdmin4 package); WB is setup to autoload the >table row count and 10 rows. I'm sticking to one set of files where they