Re: ATTACH/DETACH PARTITION CONCURRENTLY - Mailing list pgsql-hackers

From Amit Langote
Subject Re: ATTACH/DETACH PARTITION CONCURRENTLY
Date
Msg-id 1be8055c-137b-5639-9bcf-8a2d5fef6e5a@lab.ntt.co.jp
Whole thread Raw
In response to Re: ATTACH/DETACH PARTITION CONCURRENTLY  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: ATTACH/DETACH PARTITION CONCURRENTLY  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2018/11/15 11:03, Amit Langote wrote:
> As Michael pointed out, the first cleanup patch needs to be rebased due to
> a recent commit [1].  I did that to see if something we did in that commit
> made things worse for your patch, but seems fine.  I had to go and change
> things outside RelationBuildPartitionDesc as I rebased, due to the
> aforementioned commit, but they're simple changes such as changing List *
> arguments of some newly added functions to PartitionBoundSpec **.  Please
> find the rebased patches attached with this email.
> 
> [1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b52b7dc2

I noticed that the regression tests containing partitioned tables fail
randomly with the rebased patches I posted, whereas they didn't if I apply
them to HEAD without [1].

It seems to be due to the slightly confused memory context handling in
RelationBuildPartitionDesc after [1], which Alvaro had expressed some
doubts about yesterday.

I've fixed 0001 again to re-order the code so that allocations happen the
correct context and now tests pass with the rebased patches.

By the way, I noticed that the oids array added by Robert's original 0001
patch wasn't initialized to NULL, which could lead to calling pfree on a
garbage value of oids after the 2nd patch.

Thanks,
Amit

[2]
https://www.postgresql.org/message-id/20181113135915.v4r77tdthlajdlqq%40alvherre.pgsql

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: lbound1 default in buildint2vector/buildoidvector
Next
From: Noah Misch
Date:
Subject: Re: [RFC] Removing "magic" oids