Re: BUG #13860: Duplicated primary key

From: Baso10 Dev <baso10dev(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13860: Duplicated primary key
Date: 2016-01-11 23:48:57
Message-ID: CAKZHju3auXfsa0dMXUFhz2=OnGsCyur5F87w3RopXjPhMn3Jkg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Yes, I am seeing behaviour like in the link. I guess it is not a bug then.

Regards,
Domen

2016-01-12 1:39 GMT+02:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> baso10dev(at)gmail(dot)com writes:
> > I have a table A.
> > I have created table B that inherits table A.
> > After playing around I noticed there are duplicate keys in table A.
>
> Most likely, what you're seeing is the behavior described in
>
>
> http://www.postgresql.org/docs/9.4/static/ddl-inherit.html#DDL-INHERIT-CAVEATS
>
> specifically that a unique constraint on A doesn't apply to B nor
> vice versa.
>
> If that's not it, we're going to need a concrete example.
>
> regards, tom lane
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2016-01-12 01:46:28 Re: BUG #13858: Server with debugger installed consumes 100% of one CPU core
Previous Message Tom Lane 2016-01-11 23:39:16 Re: BUG #13860: Duplicated primary key