| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Nikhil Sontakke <nikkhils(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Alex Hunsaker <badalex(at)gmail(dot)com> |
| Subject: | Re: So where are we on the open commitfest? |
| Date: | 2011-11-14 18:56:15 |
| Message-ID: | CAM-w4HNV5_ZsibB7marJdEG-76u0jOHLm=FMQuRrVw8uRW92jQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 14, 2011 at 4:23 PM, Nikhil Sontakke <nikkhils(at)gmail(dot)com> wrote:
>> > * Non-inheritable check constraints
>> >
>
> So, this patch got shifted to the next commitfest...
I'm sorry, I had intended to get to it for the last two weekends. I'm
not going to wait until the commitfest to look at it.
What I want to test is that it behaves sanely when you add and remove
children to the inheritance graph. Other than that I expect it should
be pretty non-controversial and useful.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-11-14 18:56:43 | Re: Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers |
| Previous Message | Erik Rijkers | 2011-11-14 18:54:57 | Re: Cause of intermittent rangetypes regression test failures |