Re: Table partitioning with sequence field in postgresql12

From: Srinivasa T N <seenutn(at)gmail(dot)com>
To: amul sul <sulamul(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Table partitioning with sequence field in postgresql12
Date: 2020-06-18 07:03:52
Message-ID: CAFruNddSbJG_BZd6Zc1TVHNnn_5ViFAnXWpAd0jD2PzXWP-73A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I am using declarative partitioning on some other field of the same table
in which gid also exists.

Regards,
Seenu.

On Thu, Jun 18, 2020 at 12:31 PM amul sul <sulamul(at)gmail(dot)com> wrote:

> On Thu, Jun 18, 2020 at 12:22 PM Srinivasa T N <seenutn(at)gmail(dot)com> wrote:
> >
> > Hi,
> > I have a parent table with one of the field as ""gid" int4 DEFAULT
> nextval('"ami_smart_new".aoi_boundary_gid_seq'::regclass)".
> >
> > I create child tables which inherit parent and use hash partition.
> When I directly insert into child tables, will there be any race condition
> causing two child tables getting the same sequence value for gid?
> >
> if "gid" is the partitioning key and assuming you are using declarative
> partitioning[1], then it won't be possible to have the same "gid" value in
> two
> child partitions.
>
> 1] https://www.postgresql.org/docs/current/ddl-partitioning.html
>
> regards,
> Amul
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Toomas Kristin 2020-06-18 07:09:00 Re: Conflict with recovery on PG version 11.6
Previous Message amul sul 2020-06-18 07:00:55 Re: Table partitioning with sequence field in postgresql12