From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
---|---|
To: | Arne Roland <A(dot)Roland(at)index(dot)de> |
Cc: | Sand Stone <sand(dot)m(dot)stone(at)gmail(dot)com>, Rick Otten <rottenwindfish(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: dsa_allocate() faliure |
Date: | 2019-01-28 18:56:01 |
Message-ID: | CAEepm=0p5nJDAjZoqa9ovdJC_sDwbhWcwBCkVS_iSEtXR9ZYYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Tue, Jan 29, 2019 at 2:50 AM Arne Roland <A(dot)Roland(at)index(dot)de> wrote:
> does anybody have any idea what goes wrong here? Is there some additional information that could be helpful?
Hi Arne,
This seems to be a bug; that error should not be reached. I wonder if
it is a different manifestation of the bug reported as #15585 (ie some
type of rare corruption). Are you able to reproduce this
consistently? Can you please show the query plan?
--
Thomas Munro
http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2019-01-28 19:00:33 | Re: Early WIP/PoC for inlining CTEs |
Previous Message | Stephen Frost | 2019-01-28 18:43:42 | Re: pgsql: Remove references to Majordomo |
From | Date | Subject | |
---|---|---|---|
Next Message | Saurabh Nanda | 2019-01-29 01:44:15 | Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? |
Previous Message | Saurabh Nanda | 2019-01-28 16:56:49 | Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? |