|From:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>|
|To:||Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>|
|Cc:||Pg Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: partitioned tables referenced by FKs|
|Views:||Raw Message | Whole Thread | Download mbox|
On 2019-Jan-21, Amit Langote wrote:
> On 2018/12/01 4:12, Alvaro Herrera wrote:
> > Here's a more credible version of this patch series.
> Are you going to post rebased patches soon?
Yes, very soon -- right now, in fact :-)
Two preliminary patches in this series are already pushed, per a nearby
bugfix. I also split out the new index_get_partition routine to
catalog/partition.c, per comment from Jesper, and put it on its own
patch. 0003 is the interesting bits in this submission.
Note that there is a change in constraint naming on partitions. This
affects some preexisting test output ... and I'm not liking the changes
much, anymore. I'll have a look about how to revert to the previous
As you noticed in the other thread, the part of the FK clone routine
that attaches to an existing constraint needed to be refactored into its
own routine. I did that, though the split is different from what you
Jesper also mentioned removing the "#if 0" code. Actually what I need
to be doing is reinstating that check in the cases where it's possible.
I haven't done that yet.
I also dropped the part that changed how psql reports constraints in \d,
since there's a separate commitfest entry for that one.
Hmm, I just noticed that there's an ereport that fails i18n by way of
using a ternary operator in the first argument of errmsg.
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
|Next Message||Isaac Morland||2019-01-22 21:47:10||Re: Strange query behaviour|
|Previous Message||David Rowley||2019-01-22 21:44:10||Re: Delay locking partitions during query execution|