Re: suggestion about time based partitioning and hibernate - Mailing list pgsql-general

From Ron
Subject Re: suggestion about time based partitioning and hibernate
Date
Msg-id f442c75b-49b3-e273-eefc-1641c04d6f7d@gmail.com
Whole thread Raw
In response to Re: suggestion about time based partitioning and hibernate  (Luca Ferrari <fluca1978@gmail.com>)
List pgsql-general
On 7/20/23 10:31, Luca Ferrari wrote:
> On Wed, Jul 19, 2023 at 6:45 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>> Therefore I suggest to avoid doing
>> that.  Either look at some other partitioning scheme that doesn't
>> involve adding columns to the primary key, or disregard partitioning for
>> this table entirely.
> What do you mean by "other partitioning scheme"? There is nothing that
> comes into my mind at the moment.
> The problem is that, unluckily, the table is already greater than 50GB
> in seize and is keep growing, so I guess something has to be done, at
> least for a manainance point of view.
>
> Would a partition by hash on the single column primary key be such a bad idea?

Just do a range partition by the existing PK.

-- 
Born in Arizona, moved to Babylonia.



pgsql-general by date:

Previous
From: Chuck Davis
Date:
Subject: Re: My 1st JDBC and PostgreSQL
Next
From: Albrecht Dreß
Date:
Subject: pg_upgradecluster fails if pg_hba.conf contains "@file" entries