Re: move PartitionBoundInfo creation code - Mailing list pgsql-hackers

From Amit Langote
Subject Re: move PartitionBoundInfo creation code
Date
Msg-id 10bbd618-cbe3-6e56-1195-794a0a7cfcd1@lab.ntt.co.jp
Whole thread Raw
In response to Re: move PartitionBoundInfo creation code  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: move PartitionBoundInfo creation code  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2018/11/08 12:59, Amit Langote wrote:
> It might be okay to split the big switch in partition_bounds_create() into
> different functions for different partitioning methods for clarity as you
> say, but let's avoid creating new files for range, list, and hash.
> 
> I will post an updated patch with that break down.

And here is the new version.  The break down into smaller local functions
for different partitioning methods is in patch 0002.

Thanks,
Amit

Attachment

pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: Adding a TAP test checking data consistency on standby with minRecoveryPoint
Next
From: Michael Paquier
Date:
Subject: Re: Adding a TAP test checking data consistency on standby withminRecoveryPoint