On Wed, Dec 6, 2017 at 6:17 AM, Mark Dilger <hornschnor...@gmail.com> wrote:
> I'm not asking for help configuring my system. If this is a run of the mill
> out of memory
> type error, I'll deal with it myself. But if this indicates a bug, I'll be
> happy to try to distill
> what I'm doing to a test case that I can share. (I've only hit this once,
> and have little
> idea whether it would be reproducible.) The gist of the query was an
> array_agg over
> the results of a parallel query over a partitioned table, executed from
> within a plpgsql
> function, like:
>
> SELECT ARRAY_AGG((a, latest, timelogged, b, cnt)::custom_composite_type) AS
> trans FROM
> (SELECT a, b, timelogged, MAX(timelogged) OVER (PARTITION BY a) AS
> latest, SUM(cnt) AS cnt FROM
> (SELECT a, b, timelogged, COUNT(*) AS cnt
> FROM mytable
> WHERE a=
> ANY('{65537,65538,65539,65540,65541,65542,65543,65544}'::OID[])
> AND timelogged >= '2017-12-04 16:12:50-08'::TIMESTAMP
> AND timelogged < '2017-12-04 17:12:50-08'::TIMESTAMP
> GROUP BY a, b, timelogged
> ) AS ss
> GROUP BY a, b, timelogged
> ) AS s
Hi Mark,
Does the plan have multiple Gather nodes with Parallel Bitmap Heap Scan?
https://www.postgresql.org/message-id/flat/CAEepm%3D0Mv9BigJPpribGQhnHqVGYo2%2BkmzekGUVJJc9Y_ZVaYA%40mail.gmail.com
--
Thomas Munro
http://www.enterprisedb.com
