Re: explain

On Fri, 2025-04-25 at 12:36 +1200, David Rowley wrote: > On Fri, 25 Apr 2025 at 03:06, Laurenz Albe wrote: > > On Fri, 2025-04-25 at 01:41 +1200, David Rowley wrote: > > > The 79.3 seconds is the total time spent doing reads for all parallel > > > workers. 52.6 seconds is the wall clock time elaps

Re: explain

On Fri, 25 Apr 2025 at 03:06, Laurenz Albe wrote: > > On Fri, 2025-04-25 at 01:41 +1200, David Rowley wrote: > > The 79.3 seconds is the total time spent doing reads for all parallel > > workers. 52.6 seconds is the wall clock time elapsed to execute the > > query. > > But wouldn't it read "loops=

Re: pg_comebinebackup

> On 24 Apr 2025, at 20:29, Phil Florent wrote: > > Hi, > Not really a bug but I see in the feature matrix a small typo > ,https://www.postgresql.org/about/featurematrix/ > Feature Matrix - PostgreSQL > 17 16 15 14 13 12 11 10 9.6 9.5 9.4 9.3 9.2 9.1 9.0 8.4 8.3 8.2 8.1; > ANY_VALUE aggregate:

pg_comebinebackup

Hi, Not really a bug but I see in the feature matrix a small typo ,https://www.postgresql.org/about/featurematrix/ Feature Matrix - PostgreSQL 17 16 15 14 13 12 11 10 9.6 9.5 9.4 9.3 9.2 9.1 9.0 8.4 8.3 8.2 8.1; ANY_VALUE aggregate: Yes: Yes: No: N

Re: explain

On Fri, 2025-04-25 at 01:41 +1200, David Rowley wrote: > On Fri, 25 Apr 2025 at 01:32, Marc Millas wrote: > > Nested Loop Left Join (cost=941400.77..966327.57 rows=3 width=653) (actual > > time=52655.694..62533.811 rows=346 loops=1) > > Buffers: shared hit=10068265 read=396705 dirtied=1858 wri

Re: explain

Thanks ! Marc MILLAS Senior Architect +33607850334 www.mokadb.com On Thu, Apr 24, 2025 at 3:41 PM David Rowley wrote: > On Fri, 25 Apr 2025 at 01:32, Marc Millas wrote: > > Nested Loop Left Join (cost=941400.77..966327.57 rows=3 width=653) > (actual time=52655.694..62533.811 rows=346 loops=

Re: explain

On Fri, 25 Apr 2025 at 01:32, Marc Millas wrote: > Nested Loop Left Join (cost=941400.77..966327.57 rows=3 width=653) (actual > time=52655.694..62533.811 rows=346 loops=1) > Buffers: shared hit=10068265 read=396705 dirtied=1858 written=218, temp > read=429687 written=115187 > I/O Timings: r

explain

hello, there is something I seem missing in explain analyze buffers results when track_io_timing is on: this is the first lines of an explain: (the request is of no interest, such a result is quite frequent) Nested Loop Left Join (cost=941400.77..966327.57 rows=3 width=653) (actual time=52655.6

Re: Another documentation issue

On 23.04.25 11:14, Daniel Gustafsson wrote: On 23 Apr 2025, at 09:16, Laurenz Albe wrote: On Wed, 2025-04-23 at 00:21 -0500, Igor Korot wrote: However, this page https://www.postgresql.org/docs/current/runtime-config-resource.html#GUC-EFFECTIVE-IO-CONCURRENCY describes both default and mn/max