Re: Excessive memory usage in multi-statement queries w/ partitioning

From: Julian Schauder <julian(dot)schauder(at)credativ(dot)de>
To: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Andreas Seltenreich <andreas(dot)seltenreich(at)credativ(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Excessive memory usage in multi-statement queries w/ partitioning
Date: 2019-05-23 09:18:37
Message-ID: ab06f6d3b4a1775d7a05c03c5b311711f7bb2cc6.camel@credativ.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hey David,

> "multiple statements in a single query", did you mean to write
> session
> or maybe transaction there?

Maybe the wording isn't perfect. It is required that the querys are
sent as a single batch. Try the exact bash-script Andreas used for
updating the parent.

> Which version?

Tested including 11.2. Initially found on 11.1. Memory-consumption
Scales somewhat linearly with existing partitions and ';' delimited
Querys per single Batch.

regards
--
Julian Schauder

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-05-23 09:31:38 Re: "long" type is not appropriate for counting tuples
Previous Message David Rowley 2019-05-23 09:02:40 Should we warn against using too many partitions?