pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: James Pang (chaolpan) <chaolpan@cisco.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: partition pruning only works for select but update
Date: Fri, 1 Jul 2022 08:13:11 -0500
Message-ID: <20220701131311.GC13040@telsasoft.com> (raw)
In-Reply-To: <PH0PR11MB5191A8D08D5B27D084BC6BFBD6BD9@PH0PR11MB5191.namprd11.prod.outlook.com>
References: <PH0PR11MB519134D4171A126776E3E063D6B89@PH0PR11MB5191.namprd11.prod.outlook.com>
	<2391513.1656423000@sss.pgh.pa.us>
	<PH0PR11MB519143DAE98DDDAC0E1AB717D6B89@PH0PR11MB5191.namprd11.prod.outlook.com>
	<PH0PR11MB5191A8D08D5B27D084BC6BFBD6BD9@PH0PR11MB5191.namprd11.prod.outlook.com>

On Fri, Jul 01, 2022 at 08:30:40AM +0000, James Pang (chaolpan) wrote:
> We have other application depend on V13, possible to backport code changes to V13 as https://git.postgresql.org/gitweb/?p=postgresql.git;a=patch;h=86dc90056dfdbd9d1b891718d2e5614e3e432f...

Do you mean that the other application needs to be updated to work with v14?
Or that you haven't checked yet if they work with v14?

In any case, I'm sure the feature won't be backpatched to v13 - it's an
improvement but not a bugfix.

-- 
Justin

> -----Original Message-----
> From: Tom Lane <tgl@sss.pgh.pa.us> 
> Sent: Tuesday, June 28, 2022 9:30 PM
> To: James Pang (chaolpan) <chaolpan@cisco.com>
> Cc: pgsql-performance@lists.postgresql.org
> Subject: Re: partition pruning only works for select but update
> 
> "James Pang (chaolpan)" <chaolpan@cisco.com> writes:
> > But when
> > Explain update table set .. where  partitionkey between  to_timestamp() and to_timestamp();
> >   It still show all of partitions with update ...
> 
> In releases before v14, partition pruning is far stupider for UPDATE (and DELETE) than it is for SELECT.





view thread (7+ messages)  latest in thread

Message-ID: <20220701131311.GC13040@telsasoft.com>
Permalink:  ../20220701131311.GC13040@telsasoft.com/
Also on:    postgresql.org/message-id/20220701131311.GC13040@telsasoft.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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: pryzby@telsasoft.com, chaolpan@cisco.com, tgl@sss.pgh.pa.us, pgsql-performance@lists.postgresql.org
  Subject: Re: partition pruning only works for select but update
  In-Reply-To: <20220701131311.GC13040@telsasoft.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