Re: Oracle to Postgres - Transform Hash Partition - Thanks!

From: David Barbour <dbarbour(at)istation(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, cmt(at)burggraben(dot)net, mmikram(at)gmail(dot)com
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Oracle to Postgres - Transform Hash Partition - Thanks!
Date: 2024-06-11 22:11:39
Message-ID: CAEMHB2RrfXL82Q7Dsh0cr5w8ZcqVm8iDAb_bMTc7hxnQWYiR9Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

First post to this list, and am sure it won't be my last, but you guys rock!

Took a bit from all three replies and got the transformation working
seamlessly.
Created temp table.
Copied data into temp from original (just in case!)
Created partitioned table using modulus 8.
Imported the data into the partitioned table.
Dropped the original table and renamed the partitioned table.

Easy, no problems. Also no 'attach'.

Thanks.

On Fri, Jun 7, 2024 at 3:31 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:

> On Thu, 2024-06-06 at 11:28 -0500, David Barbour wrote:
> > Been an Oracle DBA for quite a while and we're moving from Oracle to
> Postgres.
> >
> > I have a table that I need to transform into a hash partitioned table.
> > I've gone through all the steps to create a hash partitioned table, with
> 8 partitions such as
> >
> > create table idev.assessment_result_2023_dab_part (like
> idev.assessment_result_2023_dab)partition by hash (district_oid);
> >
> > CREATE TABLE
> idev.assessment_result_2023_dab_part_assessment_result_2023_p1 PARTITION OF
> idev.assessment_result_2023_dab_part
> > FOR VALUES WITH (modulus 64, remainder 0)
> >
> > ....etc through partition 2023_p8 FOR VALUES WITH (modulus 64, remainder
> 7)
>
> That won't do. If you use a modulus of 64, you need 64 partitions, one for
> each possible division remainder.
>
> If you want 8 partitions, you have to use modulus 8.
>
> > Now I need to 'attach' the original table. The problem I'm running into
> is
> > there are no good examples of how to define the values.
> >
> > I've tried several iterations of various 'for values', 'values', 'for
> values with',
> > etc. but they all error out.
> >
> > Here's an example:
> > alter table idev.assessment_result_2023_dab_part
> > attach partition idev.assessment_result_2023_dab for values
> with(modulus 8, remainder 1) to (modulus 8, remainder 7)
> >
> > ERROR: syntax error at or near "to" LINE 2: ..._2023_dab for values
> with(modulus 8, remainder 1) to (modulu...
>
> I think you are confused about hash partitioning.
>
> One partition is only for a single remainder. You cannot have a partition
> for
> several remainders.
>
> Hash partitioning is mostly for splitting up a table into several parts of
> roughly equal size. You decide how many partitions you want; that will
> become
> the modulus. Then you have to create that many partitions, one for each
> remainder.
>
> If you want to attach an existing table as a partition, that will only
> work if
> all rows in the table belong into that partition. Otherwise, you will get
> an
> error.
> So you typically won't be able to attach an existing table as a hash
> partition.
>
> To convert an existing table into a hash partitioned table, you have to
>
> - create a new, empty partitioned table with *all* its partitions
>
> - transfer the data with "INSERT INTO hash_part_tab SELECT * FROM tab"
>
> Yours,
> Laurenz Albe
>

--

*David A. Barbour*

*dbarbour(at)istation(dot)com <dbarbour(at)istation(dot)com>*

*(214) 292-4096*

Istation

8150 North Central Expressway, Suite 2000

Dallas, TX 75206

www.Istation.com <http://www.istation.com/>

CONFIDENTIALITY / PROPRIETARY NOTICE:

The information contained in this e-mail, including any attachment(s), is
confidential information that may be privileged and exempt from disclosure
under applicable law. If the reader of this message is not the intended
recipient, or if you received this message in error, then any direct or
indirect disclosure, distribution or copying of this message is strictly
prohibited. If you have received this message in error, please notify
Istation by calling 866-883-7323 immediately and by sending a return
e-mail; delete this message; and destroy all copies, including attachments.

Thank you.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2024-06-11 22:25:16 Re: Does trigger only accept functions?
Previous Message Koen De Groote 2024-06-11 21:42:51 Re: Questions on logical replication