From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fwd: Core dump with nested CREATE TEMP TABLE |
Date: | 2015-09-02 06:13:03 |
Message-ID: | 55E6936F.3060308@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/1/15 11:59 PM, Michael Paquier wrote:
> On Wed, Sep 2, 2015 at 12:59 PM, Jim Nasby wrote:
>> On 9/1/15 8:42 PM, Michael Paquier wrote:
>> The crash is triggered by having an exception raised in this particular call
>> stack. Since there's no syntax error in master/0.2.1, there's no assert
>> failure either. Were you running asserts?
>
> I thought I was, but visibly it was mistaken. So, after re-rolling
> configure, I have been able to reproduce the crash, and as far as I
> can see all supported versions are impacted. I tested down to 9.1
> where extensions were introduced, and the stack trace, as well as the
> assertion failing are the same, similar to what Jim has reported. I am
> just digging more into this thing now.
I just had a theory that reference counts were messed up because there
was both a temp table and a real table with the same name. Turns out
that's not the case, but I do now know that the assert is failing for
the reference count on the temp table.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2015-09-02 06:21:37 | Re: Fwd: Core dump with nested CREATE TEMP TABLE |
Previous Message | Etsuro Fujita | 2015-09-02 06:05:22 | Re: Horizontal scalability/sharding |