Re: Partition By Range Without PrimaryKey : Postgresql Version 12.8 on AWS RDS

Adverse affects, huh?  Us, too.  Had to departition quite a few tables for
performance reasons.

Honestly, 80M rows isn't a lot, *unless* those jsonb fields are big. 
Question whether you /need/ to partition the table.

On 5/22/23 02:08, Phani Prathyush Somayajula wrote:
>
> If I had the partition column in my PK, other services using this table,
> are affected adversely – that’s the catch.
>
> Apologies for not being completely transparent.
>
> Regards,
>
> Phani Pratz
>
> PPBET-DBA
>
> *From:*Ron <ronljohnsonjr(at)gmail(dot)com>
> *Sent:* Monday, May 22, 2023 12:34 PM
> *To:* pgsql-admin(at)lists(dot)postgresql(dot)org
> *Subject:* Re: Partition By Range Without PrimaryKey : Postgresql Version
> 12.8 on AWS RDS
>
> On 5/22/23 01:53, Phani Prathyush Somayajula wrote:
>
> Hi All,
>
> I’ve a table ermabet having 80mil records. My business need is to
> check the bet placed by a player(users), which queries the table, and
> enable streaming for the player only if he has placed his bet in the
> last 24 hrs( granular to the millisecond).
>
> [snip]
>
> But I don’t want */PLACEDON/* column part of the primary key.
>
>
> And I didn't want partition_date in my PK, either, but I had to add so as
> to partition on the part_date column.
>
> --
> Born in Arizona, moved to Babylonia.
>

--
Born in Arizona, moved to Babylonia.