pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: Amit Langote <amitlangote09@gmail.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David Rowley <david.rowley@2ndquadrant.com>
Cc: Imai, Yoshikazu <imai.yoshikazu@jp.fujitsu.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: speeding up planning with partitions
Date: Fri, 22 Feb 2019 12:01:46 -0600
Message-ID: <20190222180146.GH28750@telsasoft.com> (raw)
In-Reply-To: <CA+HiwqEUwfg4s=4=is-+7k-WM-2Gs9K3iFB96QNm_eafcBozqQ@mail.gmail.com>
References: <7453.1550518972@sss.pgh.pa.us>
	<0a70234e-b2e6-debc-2fb5-e8fd927caa00@lab.ntt.co.jp>
	<1002.1550596071@sss.pgh.pa.us>
	<30961.1550609873@sss.pgh.pa.us>
	<250c61bc-479c-92f4-d19d-d768e3bcdcbc@lab.ntt.co.jp>
	<13510.1550677844@sss.pgh.pa.us>
	<a47e6214-bd46-ab4b-2f84-f9f726e04642@lab.ntt.co.jp>
	<35b02675-83c2-a12b-961a-fec249b06f35@lab.ntt.co.jp>
	<20190222165932.GG28750@telsasoft.com>
	<CA+HiwqEUwfg4s=4=is-+7k-WM-2Gs9K3iFB96QNm_eafcBozqQ@mail.gmail.com>

On Sat, Feb 23, 2019 at 02:54:35AM +0900, Amit Langote wrote:
> > On Fri, Feb 22, 2019 at 09:45:38PM +0900, Amit Langote wrote:
> > > I have updated the inheritance expansion patch.
> > >
> > > Patch 0001 rewrites optimizer/utils/inherit.c, so that it allows
> >
> > Thanks for your continued work on this.
> >
> > I applied v23 patch and imported one of our customers' schema, and ran explain
> > on a table with 210 partitions.  With patch applied there are 10x fewer system
> > calls, as intended.
> 
> OK, great.  I guess you were running SELECT?  Just in case you missed,
> the patch to improve UPDATE/DELETE scalability is no longer part of
> this patch series.

Yes, I understand the scope is reduced.

Actually, when I tested last month, I don't think I realized that UPDATE/DELETE
was included.  Otherwise I would've also tested to see if it resolves the
excessive RAM use with many partitions, with the explanation given that query
is being replanned for every partition.

I set target version to v12.
https://commitfest.postgresql.org/22/1778/

Justin




view thread (265+ messages)  latest in thread

Message-ID: <20190222180146.GH28750@telsasoft.com>
Permalink:  ../20190222180146.GH28750@telsasoft.com/
Also on:    postgresql.org/message-id/20190222180146.GH28750@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-hackers@postgresql.org
  Cc: pryzby@telsasoft.com, amitlangote09@gmail.com, Langote_Amit_f8@lab.ntt.co.jp, tgl@sss.pgh.pa.us, david.rowley@2ndquadrant.com, imai.yoshikazu@jp.fujitsu.com, alvherre@2ndquadrant.com
  Subject: Re: speeding up planning with partitions
  In-Reply-To: <20190222180146.GH28750@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