Re: Postgres server 12.2 crash with process exited abnormally and possibly corrupted shared memory

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Ishan Joshi <Ishan(dot)Joshi(at)amdocs(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Postgres server 12.2 crash with process exited abnormally and possibly corrupted shared memory
Date: 2020-06-10 16:58:11
Message-ID: CAHOFxGp=vOdgKerNp6oPDJdmHjPuU9aLgOHr=aBEoW=4aqabiw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jun 10, 2020 at 12:05 AM Ishan Joshi <Ishan(dot)Joshi(at)amdocs(dot)com> wrote:

> How many rows did these tables have before partitioning? à We starts
> test with 0 rows in partition table.
>

Partitions are far from free and pruning is great but not guaranteed. How
many total rows do you currently have or foresee having in the biggest
table (all partitions combined, or without partitioning) within the next
1-3 years? 1 million? 100 million? 2 billion? You may have partitioned
before it was prudent to do so is the point. Just because something can be
done, doesn't mean it should be. What sort of key are you partitioning on?

Also, what do you mean about tests? There are some assumptions made about
empty tables since stats may indicate they are empty when they are not. If
your tests involve many empty tables, then it may give rather different
performance than real life where there are few or no empty partitions.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ishan Joshi 2020-06-10 17:11:44 RE: Postgres server 12.2 crash with process exited abnormally and possibly corrupted shared memory
Previous Message PEDRO PABLO SEVERIN HONORATO 2020-06-10 16:57:53 Re: Help with plpython3u