Skip site navigation (1) Skip section navigation (2)

Meeting Tuesday, November 15: Managing High Volume Writes

From: Greg <gsmith(at)gregsmith(dot)com>
To: bwpug(at)postgresql(dot)org
Subject: Meeting Tuesday, November 15: Managing High Volume Writes
Date: 2011-11-10 17:40:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: bwpug
The BWPUG isn't dead, it's just been resting.  After skipping a few 
meetings because of conflicts with the fall conference season we're back 
next week.

Administration note first:  after testing out Meetup for a while, the 
page at is 
going to be the sole place to get announcements about future meetings.  
We expect to shut down this mailing list after this message.  If you'd 
like to be notified about the BWPUG, please join that group and you can 
get notifications there.

This month I'm going to present a talk on the issues around use 
PostgreSQL for high volume write applications.  PostgreSQL has worked 
well for many OLTP style application, where a number of clients are 
writing heavily to the database throughout the day.  But if you combine 
heavy write volume with archiving, eventually you'll start approaching a 
data warehouse sized database, with terabytes of data.  Designing and 
tuning PostgreSQL for a combination of heavy incoming data and a large 
archive size requires some specialized knowledge, from how the database 
cleans up after old data to how partitioning can be used for this purpose.

Topic covered will include:

-Basic database tuning for high write volume
-Monitoring buffer cache throughput
-Issues with empty cache performance
-Adjusting VACUUM cleanup
-Partitioning for time series data
-Hardware for write-heavy database workloads
-Write scaling with Skytools

When: November 15, 6:30PM.
Where: 7070 Samuel Morse Dr, Columbia, MD, 21042.
Host: OmniTI

bwpug by date

Next:From: Mitesh ShahDate: 2012-05-02 19:55:58
Subject: pg_dump: aborting because of server version mismatch
Previous:From: Robert TreatDate: 2011-08-10 14:41:44
Subject: BWPUG Moving

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group