Mladen Gogala writes:
> On 1/13/22 18:35, Tom Lane wrote:
>> .. or else reduce the number of partitions you're using. (People
>> frequently seem to think that more partitions are free. That is
>> extremely not true. I generally think that if you're using more
>> than a few dozen partitions per
On 1/13/22 18:35, Tom Lane wrote:
.. or else reduce the number of partitions you're using. (People
frequently seem to think that more partitions are free. That is
extremely not true. I generally think that if you're using more
than a few dozen partitions per table, you are making a mistake.)
Hi Tom,
This was very helpful, thanks for the tips.
Gautam
On Thu, Jan 13, 2022 at 3:36 PM Tom Lane wrote:
> Gautam Bellary writes:
> > I've got a PL/pgSQL function (regenerate_gateway_last_seen, attached)
> that
> > loops through all partitions of 2 tables ("Measure" and
> "ValuelessMeasure"
Gautam Bellary writes:
> I've got a PL/pgSQL function (regenerate_gateway_last_seen, attached) that
> loops through all partitions of 2 tables ("Measure" and "ValuelessMeasure",
> schema attached) selecting data from each into another table
> ("GatewayLastSeenNew"). Occasionally the function runs
Hi Postgres group,
I'm reaching out for some help with an "ERROR: out of shared memory. HINT:
You might need to increase max_locks_per_transaction" issue:
I've got a PL/pgSQL function (regenerate_gateway_last_seen, attached) that
loops through all partitions of 2 tables ("Measure" and "ValuelessM
