pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ron <ronljohnsonjr@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Large number of partitions of a table
Date: Mon, 17 Jan 2022 09:58:32 -0500
Message-ID: <3992395.1642431512@sss.pgh.pa.us> (raw)
In-Reply-To: <671340a5-1960-e5dc-1d09-4b7f36cda2c8@gmail.com>
References: <YeTYA63gEXNePfkv@admin.sibptus.ru>
	<3919502.1642393668@sss.pgh.pa.us>
	<YeUAx56Juri43xGY@admin.sibptus.ru>
	<671340a5-1960-e5dc-1d09-4b7f36cda2c8@gmail.com>

Ron <ronljohnsonjr@gmail.com> writes:
> On 1/16/22 11:38 PM, Victor Sudakov wrote:
>> so no query should ever have to use more than 1 partition.

> I find it hard to believe that you'll *never* run a report against more 
> customers than are in a single partition.

Yeah, I'm a little suspicious of that.  The other thing I'd be worried
about, given that the OP is using v13, is that UPDATE/DELETE planning
performance can be pretty awful with lots of partitions.  There were
some O(N^2) behaviors in there that we didn't get rid of till v14.

			regards, tom lane





view thread (22+ messages)  latest in thread

Message-ID: <3992395.1642431512@sss.pgh.pa.us>
Permalink:  ../3992395.1642431512@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3992395.1642431512@sss.pgh.pa.us

 · 

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-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Large number of partitions of a table
  In-Reply-To: <3992395.1642431512@sss.pgh.pa.us>

* 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