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

help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Large number of partitions of a table
Date: Tue, 18 Jan 2022 19:48:58 -0600
Message-ID: <6cea6b1c-9e12-2771-a2f7-d8a73ce723f3@gmail.com> (raw)
In-Reply-To: <0fdfb200-9aad-370b-3282-6585158de94f@gmail.com>
References: <YeTYA63gEXNePfkv@admin.sibptus.ru>
	<3919502.1642393668@sss.pgh.pa.us>
	<YeUAx56Juri43xGY@admin.sibptus.ru>
	<671340a5-1960-e5dc-1d09-4b7f36cda2c8@gmail.com>
	<YeYr88f3jXHlijU9@admin.sibptus.ru>
	<254601.1642480213@sss.pgh.pa.us>
	<YeZV0QSOly8Pnx5d@admin.sibptus.ru>
	<268771.1642489687@sss.pgh.pa.us>
	<YeZ3/4TSd+xHAlDl@admin.sibptus.ru>
	<d45899c8-187d-4a1d-563b-f5842243e770@gmail.com>
	<0fdfb200-9aad-370b-3282-6585158de94f@gmail.com>

On 1/18/22 6:09 PM, Mladen Gogala wrote:
> On 1/18/22 09:47, Ron wrote:
>> EXPLAIN plans are going to be hilariously gigantic, which means that 
>> query planning would take a loooong time,  And the query planner (in v12, 
>> at least) can generate some pretty bad plans in partitioned tables; I bet 
>> there are edge cases in the QP code that don't work well with 10000 
>> partitions and 50000 indices.
>
> These things sometimes happen. On the oracle-l, there is a thread in 
> progress about a generated SQL with 130,000 lines which fails parsing 
> because parsing exhausts the available memory.
>

But there wasn't any programming.  The company saved so much money!!!

> In such cases, I am less inclined to look for a fault with the database 
> software and more inclined to inflict an unusual and cruel punishment on 
> whoever has designed the data model.
>

OOP was definitely involved, in some way or form...

-- 
Angular momentum makes the world go 'round.





view thread (22+ messages)  latest in thread

Message-ID: <6cea6b1c-9e12-2771-a2f7-d8a73ce723f3@gmail.com>
Permalink:  ../6cea6b1c-9e12-2771-a2f7-d8a73ce723f3@gmail.com/
Also on:    postgresql.org/message-id/6cea6b1c-9e12-2771-a2f7-d8a73ce723f3@gmail.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-admin@postgresql.org
  Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Large number of partitions of a table
  In-Reply-To: <6cea6b1c-9e12-2771-a2f7-d8a73ce723f3@gmail.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