On Wed, Jan 4, 2017 at 11:35 AM, Tomas Vondra
<tomas.von...@2ndquadrant.com> wrote:
> On 01/03/2017 05:22 PM, Tomas Vondra wrote:
>> On 01/03/2017 02:42 PM, Dilip Kumar wrote:
> ...
>>> I think it should be easily reproducible, in case it's not I can send
>>> call stack or core dump.
>> Thanks for the report. It was trivial to reproduce and it turned out to
>> be a fairly simple bug. Will send a new version of the patch soon.
> Attached is v22 of the patch series, rebased to current master and fixing
> the reported bug. I haven't made any other changes - the issues reported by
> Petr are mostly minor, so I've decided to wait a bit more for (hopefully)
> other reviews.

And nothing has happened since. Are there people willing to review
this patch and help it proceed? As this patch is quite large, I am not
sure if it is fit to join the last CF. Thoughts?

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

Reply via email to