Re: Commit 4dba331cb3 broke ATTACH PARTITION behaviour.

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commit 4dba331cb3 broke ATTACH PARTITION behaviour.
Date: 2018-03-29 16:04:06
Message-ID: 20180329160406.ii2wgbkmlnfxtwbt@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Rushabh Lathia wrote:
> On Thu, Mar 29, 2018 at 7:46 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
> wrote:

> > Hmm, offhand I don't quite see why this error fails to be thrown.
> ATTACH PARTITION should throw an error, because partition table "foo"
> already have two partition with key values (1, 2,3 4). And table "foo_d"
> which we are attaching here has :

Oh, I understand how it's supposed to work. I was just saying I don't
understand how this bug occurs. Is it because we fail to determine the
correct partition constraint for the default partition in time for its
verification scan?

Álvaro Herrera
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2018-03-29 16:18:43 Re: [HACKERS] [POC] Faster processing at Gather node
Previous Message Jesper Pedersen 2018-03-29 15:55:00 Re: JIT compiling with LLVM v12