Re: COPY enhancements - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: COPY enhancements
Date
Msg-id 4ACCA999.1090502@dunslane.net
Whole thread Raw
In response to Re: COPY enhancements  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: COPY enhancements
List pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>   
>> Emmanuel Cecchet wrote:
>>     
>>> If you prefer to postpone the auto-partitioning to the next commit 
>>> fest, I can strip it from the current patch and re-submit it for the 
>>> next fest (but it's just 2 isolated methods really easy to review).
>>>       
>
>   
>> I certainly think this should be separated out. In general it is not a 
>> good idea to roll distinct features together. It complicates both the 
>> reviewing process and the discussion.
>>     
>
> I think though that Greg was suggesting that we need some more thought
> about the overall road map.  Agglomerating "independent" features onto
> COPY one at a time is going to lead to a mess, unless they fit into an
> overall design plan.
>
>             
>   

I don't disagree with that. But even if we get a roadmap of some set of 
features we want to implement, rolling them all together isn't a good 
way to go.

cheers

andrew




pgsql-hackers by date:

Previous
From: Gnanam
Date:
Subject: Deadlock error in INSERT statements
Next
From: Andrew Dunstan
Date:
Subject: Re: Feature Suggestion: PL/Js