Hello all,
I've spent some time looking through previous posts regarding
postgres and SSD drives and have also been reading up on the
subject of SSDs in general elsewhere.
Some quick background:
We're currently looking at changing our basic database setup as we
migrate away from some rather old
On Fri, Oct 14, 2011 at 2:35 AM, Svetlin Manavski
svetlin.manav...@gmail.com wrote:
Thank you guys for spotting the problem immediately.
The reason for such autovacuum thresholds is that these tables are designed
for very high rate of inserts and I have a specific routine to analyze them
in a
Thank you guys for spotting the problem immediately.
The reason for such autovacuum thresholds is that these tables are designed
for very high rate of inserts and I have a specific routine to analyze them
in a more controlled way. Infact the stats target of some of the fields is
also high. However
On 14-10-2011 10:23, CSS wrote:
-I'm calling our combined databases at 133GB small, fair
assumption? -Is there any chance that a server with dual quad core
xeons, 32GB RAM, and 2 or 4 SSDs (assume mirrored) could be slower
than the 4 old servers described above? I'm beating those on raw
cpu,
Vishnu,
I am using PostgreSQL 8.4 in windows. I have created a database and
some tables on it. Also created a table space and some tables in it. My
application inserts data into these tables in every second. The
application is a continuous running application. My issue is that after
a
