From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
---|---|
To: | Sabyasachi Mukherjee <mukherjee(dot)sabyasachi(at)outlook(dot)com> |
Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Loading data from one table to another |
Date: | 2024-10-13 14:34:51 |
Message-ID: | BD7CC9C3-75C7-4D7C-A5F0-09ACC9828806@elevated-dev.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Failing to allocate a memory segment of only 1MB seems suspicious. What are your hardware specs?
You might want to look at your memory & parallel query settings in postgresql.conf--perhaps some of those are set too high relative to your server's memory.
I wouldn't really expect queries to be slow on 99GB, by the way. That is not a large database. Partitioning is reasonable if you want to prune old data periodically, as then you can just drop old partitions. But unless your queries are regularly have to perform table scans, I wouldn't expect them to be slow. And if they are performing table scans, you'd need to investigate how to fix that--what indexes to add. Partitioning will get you incremental performance gains in such a case, while the right index will get you exponential gains.
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2024-10-14 06:36:08 | Re: Loading data from one table to another |
Previous Message | Holger Jakobs | 2024-10-13 10:31:00 | RE: Loading data from one table to another |