On Fri, May 6, 2016 at 11:24 AM, Andres Freund wrote:
>
>> I have been trying (and failing) to reproduce the problem in more
>> recent releases, with and without cassert. Here is pg_config output
>> of one of my current attempts:
>
> If you say "recent releases" you mean that you've not been able
On 2016-05-06 11:15:03 -0700, Jeff Janes wrote:
> > Running the test with cassert enabled I actually get assertion failures,
> > due to the FATAL you added.
> >
> > #1 0x00958dde in ExceptionalCondition (conditionName=0xb36c2a
> > "!(RefCountErrors == 0)", errorType=0xb361af "FailedAssert
On Thu, May 5, 2016 at 11:52 AM, Andres Freund wrote:
> Hi Jeff,
>
> On 2016-04-29 10:38:55 -0700, Jeff Janes wrote:
>> I don't see the problem with an cassert-enabled, probably because it
>> is just too slow to ever reach the point where the problem occurs.
>
> Running the test with cassert enabl
Hm. And you're not seeing the asserts I reported in
http://archives.postgresql.org/message-id/20160505185246.2i7qftadwhzewykj%40alap3.anarazel.de
?
I see it a lot, but I think that is a result of ereport(FATAL) after
FileWrite(BLCKSZ/3) added by Jeff.
Teodor Sigaev
On 2016-05-04 18:12:45 +0300, Teodor Sigaev wrote:
> > > I get the errors:
> > >
> > > ERROR: attempted to delete invisible tuple
> > > STATEMENT: update foo set count=count+1,text_array=$1 where text_array
> > > @> $2
> > >
> > > And also:
> > >
> > > ERROR: unexpected chunk number 1 (expec
Hi Jeff,
On 2016-04-29 10:38:55 -0700, Jeff Janes wrote:
> I don't see the problem with an cassert-enabled, probably because it
> is just too slow to ever reach the point where the problem occurs.
Running the test with cassert enabled I actually get assertion failures,
due to the FATAL you added.
I'll try to get a coredump after SIGSEGV, but it could take a time.
Got it!
#0 0x0008014321d7 in sbrk () from /lib/libc.so.7
#1 0x000801431ddd in sbrk () from /lib/libc.so.7
#2 0x00080142e5bb in sbrk () from /lib/libc.so.7
#3 0x00080142e085 in sbrk () from /lib/libc.so.7
#4
Any chance you could package up that data directory for me to download?
Sent by personal email to Alexander, Andres and Jeff
In /var/log/message I found
May 4 22:04:07 xor kernel: pid 14010 (postgres), uid 1001: exited on signal 6
(core dumped)
May 4 22:04:25 xor kernel: pid 14032 (postgres
Hi Jeff,
On 2016-05-04 14:00:01 -0700, Jeff Janes wrote:
> On Tue, May 3, 2016 at 4:05 PM, Andres Freund wrote:
> > Hm. I appear to have trouble reproducing this issue (continuing to try)
> > on master as of 8826d8507. Is there any chance you could package up a
> > data directory after the issue
On Tue, May 3, 2016 at 4:05 PM, Andres Freund wrote:
> Hi Jeff,
>
> On 2016-04-29 10:38:55 -0700, Jeff Janes wrote:
>> I've bisected the errors I was seeing, discussed in
>> http://www.postgresql.org/message-id/CAMkU=1xqehc0ok4d+tkjfq1nvuho37pyrkhjp6q8oxifmx7...@mail.gmail.com
>>
>> It look like t
On 2016-05-04 18:12:45 +0300, Teodor Sigaev wrote:
> > > I get the errors:
> > >
> > > ERROR: attempted to delete invisible tuple
> > > STATEMENT: update foo set count=count+1,text_array=$1 where text_array
> > > @> $2
> > >
> > > And also:
> > >
> > > ERROR: unexpected chunk number 1 (expec
I get the errors:
ERROR: attempted to delete invisible tuple
STATEMENT: update foo set count=count+1,text_array=$1 where text_array @> $2
And also:
ERROR: unexpected chunk number 1 (expected 2) for toast value
85223889 in pg_toast_16424
STATEMENT: update foo set count=count+1 where text_arr
On Wed, May 4, 2016 at 2:05 AM, Andres Freund wrote:
> On 2016-04-29 10:38:55 -0700, Jeff Janes wrote:
> > I've bisected the errors I was seeing, discussed in
> >
> http://www.postgresql.org/message-id/CAMkU=1xqehc0ok4d+tkjfq1nvuho37pyrkhjp6q8oxifmx7...@mail.gmail.com
> >
> > It look like they fi
Hi Jeff,
On 2016-04-29 10:38:55 -0700, Jeff Janes wrote:
> I've bisected the errors I was seeing, discussed in
> http://www.postgresql.org/message-id/CAMkU=1xqehc0ok4d+tkjfq1nvuho37pyrkhjp6q8oxifmx7...@mail.gmail.com
>
> It look like they first appear in:
>
> commit 48354581a49c30f5757c203415aa8
Hi,
On 2016-04-29 10:38:55 -0700, Jeff Janes wrote:
> I've bisected the errors I was seeing, discussed in
> http://www.postgresql.org/message-id/CAMkU=1xqehc0ok4d+tkjfq1nvuho37pyrkhjp6q8oxifmx7...@mail.gmail.com
>
> It look like they first appear in:
>
> commit 48354581a49c30f5757c203415aa8412d8
I've bisected the errors I was seeing, discussed in
http://www.postgresql.org/message-id/CAMkU=1xqehc0ok4d+tkjfq1nvuho37pyrkhjp6q8oxifmx7...@mail.gmail.com
It look like they first appear in:
commit 48354581a49c30f5757c203415aa8412d85b0f70
Author: Andres Freund
Date: Sun Apr 10 20:12:32 2016 -0
16 matches
Mail list logo
