Re: Out of memory error with PG10.3, 10.4 but not 9.3.19

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: ChatPristi <cchristo_0899(at)yahoo(dot)fr>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Out of memory error with PG10.3, 10.4 but not 9.3.19
Date: 2018-05-16 08:48:11
Message-ID: 20180516084811.GA14835@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, May 15, 2018 at 03:02:48PM +0000, ChatPristi wrote:
> I got the error with PG 10.3 and 10.4 on CentOS 7 up-to-date.The
> command works with a smaller size database.
> The command works with the same database with PG 9.3.19 on RHEL 6.9
> up-to-date.
>
> I attach the EXPLAIN SELECT command.

Well, instead of an explain output which takes 2.4MB compressed and
9.6MB uncompressed (take it as unreadable), could you produce a
self-contained test case with a glimpse of the schema you are using?
Where does the OOM happen, and how did you change your partitioned table
schema? Are you using the native partitioning instead?
--
Michael

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Philipp Kraus 2018-05-16 18:07:49 sql function with empty row
Previous Message Philipp Kraus 2018-05-16 07:15:07 Re: array_agg to array