Re: [HACKERS] Default Partition for Range - Mailing list pgsql-hackers

From Beena Emerson
Subject Re: [HACKERS] Default Partition for Range
Date
Msg-id CAOG9ApEKrmebJtt=X9YGesTDP-zBizwSGupeR41sXqNwRN7V4A@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Default Partition for Range  (Rafia Sabih <rafia.sabih@enterprisedb.com>)
Responses Re: [HACKERS] Default Partition for Range
List pgsql-hackers
Hello,

On Sun, Jun 4, 2017 at 9:26 AM, Rafia Sabih
<rafia.sabih@enterprisedb.com> wrote:
> On Fri, Jun 2, 2017 at 5:48 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Fri, Jun 2, 2017 at 8:09 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>>> I think if you have found spelling mistakes unrelated to this patch,
>>> then it is better to submit those as a separate patch in a new thread.
>>
>> +1.
>
> Sure, attached is the version without those changes.
>

Thank you for your comments. I have applied most of the changes. The
regression comment change from 'fail' -> ' Following statement should
fail' and 'ok' -> 'Following should complete successfully' is ignored
since other tests in the file had similar comments

The new patch is rebased over default_partition_v18.patch
[http://www.mail-archive.com/pgsql-hackers@postgresql.org/msg315831.html]


-- 

Beena Emerson

EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [HACKERS] PostgreSQL 10 changes in exclusion constraints - didsomething change? CASE WHEN behavior oddity
Next
From: Noah Misch
Date:
Subject: Re: [HACKERS] Continuous buildfarm failures on hamster with bin-check