Re: Postgres server 12.2 crash with process exited abnormally andpossibly corrupted shared memory - Mailing list pgsql-general

From Michael Lewis
Subject Re: Postgres server 12.2 crash with process exited abnormally andpossibly corrupted shared memory
Date
Msg-id CAHOFxGp=vOdgKerNp6oPDJdmHjPuU9aLgOHr=aBEoW=4aqabiw@mail.gmail.com
Whole thread Raw
In response to RE: Postgres server 12.2 crash with process exited abnormally andpossibly corrupted shared memory  (Ishan Joshi <Ishan.Joshi@amdocs.com>)
Responses RE: Postgres server 12.2 crash with process exited abnormally andpossibly corrupted shared memory  (Ishan Joshi <Ishan.Joshi@amdocs.com>)
List pgsql-general
On Wed, Jun 10, 2020 at 12:05 AM Ishan Joshi <Ishan.Joshi@amdocs.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.


pgsql-general by date:

Previous
From: PEDRO PABLO SEVERIN HONORATO
Date:
Subject: Re: Help with plpython3u
Next
From: Ishan Joshi
Date:
Subject: RE: Postgres server 12.2 crash with process exited abnormally andpossibly corrupted shared memory