On Wed, May 17, 2017 at 5:34 PM, Noah Misch wrote:
> [Action required within three days. This is a generic notification.]
>
> The above-described topic is currently a PostgreSQL 10 open item. Robert,
> since you committed the patch believed to have created it, you own this
> On May 15, 2017, at 9:37 PM, Amit Langote
> wrote:
>
> On 2017/05/16 1:18, Mark Dilger wrote:
>>
>>> On May 15, 2017, at 6:49 AM, Mark Dilger wrote:
>>>
>>> I can confirm that this fixes the crash that I was seeing. I have read
>>>
On 2017/05/16 1:18, Mark Dilger wrote:
>
>> On May 15, 2017, at 6:49 AM, Mark Dilger wrote:
>>
>> I can confirm that this fixes the crash that I was seeing. I have read
>> through the patch briefly, but will give it a more thorough review in the
>> next few hours.
> On May 15, 2017, at 6:49 AM, Mark Dilger wrote:
>
> I can confirm that this fixes the crash that I was seeing. I have read
> through the patch briefly, but will give it a more thorough review in the
> next few hours.
My only negative comment is that your patch
> On May 14, 2017, at 11:02 PM, Amit Langote
> wrote:
>
> On 2017/05/14 12:03, Mark Dilger wrote:
>> Hackers,
>>
>> I discovered a reproducible crash using event triggers in the current
>> development version, 29c7d5e483acaa74a0d06dd6c70b320bb315.
>> I was
On 2017/05/14 12:03, Mark Dilger wrote:
> Hackers,
>
> I discovered a reproducible crash using event triggers in the current
> development version, 29c7d5e483acaa74a0d06dd6c70b320bb315.
> I was getting a crash before this version, and cloned a fresh copy of
> the sources to be sure I was up