Andres Freund writes:
> Hi,
>
> On 2019-06-17 21:46:02 -0400, Steve Singer wrote:
>> On 6/15/19 10:18 PM, Tom Lane wrote:
>> > Steve Singer writes:
>> > > I encountered the following segfault when running against a PG 12 beta1
>> > > during a analyze against a table.
>> > Nobody else has report
Hi,
On 2019-06-17 21:46:02 -0400, Steve Singer wrote:
> On 6/15/19 10:18 PM, Tom Lane wrote:
> > Steve Singer writes:
> > > I encountered the following segfault when running against a PG 12 beta1
> > > during a analyze against a table.
> > Nobody else has reported this, so you're going to have t
Andres Freund writes:
> On 2019-06-18 00:32:17 -0400, Tom Lane wrote:
>> Hmm, that's a pretty obvious mistake :-( but after some fooling around
>> I've not been able to cause a crash with it. I wonder what test case
>> you were using, on what platform?
> I suspect that's because the bug is "only
On 6/18/19 12:32 AM, Tom Lane wrote:
Steve Singer writes:
The attached patch fixes the issue.
Hmm, that's a pretty obvious mistake :-( but after some fooling around
I've not been able to cause a crash with it. I wonder what test case
you were using, on what platform?
Hi,
On 2019-06-18 00:32:17 -0400, Tom Lane wrote:
> Steve Singer writes:
> > The attached patch fixes the issue.
>
> Hmm, that's a pretty obvious mistake :-( but after some fooling around
> I've not been able to cause a crash with it. I wonder what test case
> you were using, on what platform?
Steve Singer writes:
> The attached patch fixes the issue.
Hmm, that's a pretty obvious mistake :-( but after some fooling around
I've not been able to cause a crash with it. I wonder what test case
you were using, on what platform?
regards, tom lane
On 6/15/19 10:18 PM, Tom Lane wrote:
Steve Singer writes:
I encountered the following segfault when running against a PG 12 beta1
during a analyze against a table.
Nobody else has reported this, so you're going to have to work on
producing a self-contained test case, or else debugging it your
Steve Singer writes:
> I encountered the following segfault when running against a PG 12 beta1
> during a analyze against a table.
Nobody else has reported this, so you're going to have to work on
producing a self-contained test case, or else debugging it yourself.
regar
