From: | Fabio Isabettini <fisabettini(at)voipfuture(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: dsa_allocate() faliure |
Date: | 2019-01-30 09:53:24 |
Message-ID: | 9663C144-68A3-4BD1-89E9-9D97E180E750@voipfuture.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Hi Thomas,
it is a Production system and we don’t have permanent access to it.
Also to have an auto_explain feature always on, is not an option in production.
I will ask the customer to give us notice asap the error present itself to connect immediately and try to get a query plan.
Regards
Fabio Isabettini
www.voipfuture.com
> On 30. Jan 2019, at 04:13:14, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> wrote:
>
> On Tue, Jan 29, 2019 at 10:32 PM Fabio Isabettini
> <fisabettini(at)voipfuture(dot)com> wrote:
>> we are facing a similar issue on a Production system using a Postgresql 10.6:
>>
>> org.postgresql.util.PSQLException: ERROR: EXCEPTION on getstatistics ; ID: EXCEPTION on getstatistics_media ; ID: uidatareader.
>> run_query_media(2): [a1] REMOTE FATAL: dsa_allocate could not find 7 free pages
>
>> We would like not to stop the Production system and upgrade it to PG11. And even though would this guarantee a permanent fix?
>> Any suggestion?
>
> Hi Fabio,
>
> Thanks for your report. Could you please also show the query plan
> that runs on the "remote" node (where the error occurred)?
>
> There is no indication that upgrading to PG11 would help here. It
> seems we have an undiagnosed bug (in 10 and 11), and so far no one has
> been able to reproduce it at will. I personally have chewed a lot of
> CPU time on several machines trying various plan shapes and not seen
> this or the possibly related symptom from bug #15585 even once. But
> we have about three reports of each of the two symptoms. One reporter
> wrote to me off-list to say that they'd seen #15585 twice, the second
> time by running the same query in a tight loop for 8 hours, and then
> not seen it again in the past 3 weeks. Clearly there is issue needing
> a fix here, but I don't yet know what it is.
>
> --
> Thomas Munro
> http://www.enterprisedb.com
>
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2019-01-30 09:56:32 | Re: WIP: Avoid creation of the free space map for small tables |
Previous Message | Alexander Korotkov | 2019-01-30 08:59:18 | Re: jsonpath |
From | Date | Subject | |
---|---|---|---|
Next Message | Mariel Cherkassky | 2019-01-30 10:35:56 | Re: ERROR: found xmin from before relfrozenxid |
Previous Message | Alvaro Herrera | 2019-01-30 09:13:59 | Re: ERROR: found xmin from before relfrozenxid |