I already did the long conference entry here, so just a quick update: slides from PGEast are posted and next week I'll be at the increasingly misnamed MySQL Conference in Santa Clara, California.One thing I'm known for now is ranting about cheap Solid State Drives and how they suck for database use. The Reliable Writes wiki page collects up most of the background here. The situation the last few years has been that every inexpensive drive on the market does not have a safe write cache for database use. Every customer of mine who has purchased one of Intel's SSD drives for example, either the X25-M or the not-enterprise-at-all X25-E, has suffered at least one massive data corruption loss.In order to make a flash drive safe, you need to have a battery-backup on the
Some members of the Greenplum Community Forum have been asking about how to install on Greenplum CE a very useful "contrib" module available for PostgreSQL.
This week's water falling from the skies isn't turning into snow. And on days when it's clear, my car is covered with tree pollen. While they means something different to most people, to me these are the signs that the spring conference season is about to start. There's a conference in North America during each of the next three months containing serious PostgreSQL content, and this year I'm making each of them.PgEast 2011 takes place in New York City starting just over two weeks from now. If you're nearby, it's not too late to make travel plans. The location is so easy to reach via train. The conference venue is right on top of New York's Penn Station, a major train hub. All the major East Coast cities from Boston to Richmond are easy rides from
for getting details, schedules and prises.Of course besides trainings we offer the whole 2ndQuadrant portfolio.You want that somebody will visit you and help you with your PostgreSQL System?Then 2ndQuadrant is the right address for you, Just contact us.You want to migrate from another DBMS to PostgreSQL and need help / (more…)
We are proud to announce that 2ndQuadrant Deutschland (Germany) officially is registered.As opening bargain ...We offer 11 different German PostgreSQL trainings, workshops and crash courses between March and July in Bielefeld for special prises.Topics are about PostgreSQL Administration, Performance tuning, Replication, Advanced Development, SQL and Database Basics. Our special PostgreSQL for MySQLer training is on the list too.Please contact
Following up on last month's Tuning Linux for low PostgreSQL Latency, there's now been a giant pile of testing done on two filesystems, three patches, and two sets of kernel tuning parameters run. The result so far is some interesting new data, and one more committed improvements in this area that are in PostgreSQL 9.1 now (making three total, the other two are monitoring patches). I'll be speaking about recommended practice next month during one of my talks at PostgreSQL East, and I've submitted something in this area for May's PGCon too. Here I'll talk a bit more about the dead ends too, while those memories are still fresh.
The basic problem here is that the way PostgreSQL uses the operating system cache when writing allows large amounts of data to accumulate. The result when
Lots of PostegreSQLer also use MySQL.Lots of MySQLer want to use PostgreSQL too.You are MySQLer and want to get more knowledge about PostgreSQL?2ndQuadrant and me are planning to offer special PostgreSQL trainings forMySQLers / MySQL Administrators.Depending on attendees the training will be in English or German.It is planned to do the first training in Bielefeld area (Germany).Also we are thinking about Amsterdam.Other locations might follow.If you have interests to attend the training just contact me for getting more details.
One of the challenges when dealing with a new database design is that you don't know things like how big the tables will end up being until they're actually populated with a fair amount of data. But if the design has to factor in the eventual scalability concerns, you can't deploy it to obtain that data until the estimation is done. One way around this is to aggressively prototype things. Use staging hardware for this purpose that new applications can live on temporarily while sorting details like this out. You can just factor in that you'll need to move the app and possibly redesign it after a few months, when you have a better idea what data is going to show up in it.The other way to get around this chicken/egg problem is to write a data generator. Construct
This week's flame war on the pgsql-performance list once again revolves around the fact that PostgreSQL doesn't have the traditional hint syntax available in other databases. There are a mix of technical and pragmatic reasons behind why that is: Introducing hints is a common source of later problems, because fixing a query place once in a special case isn't a very robust approach. As your data set grows, and possibly changes distribution as well, the idea you hinted toward when it was small can become an increasingly bad idea.Adding a useful hint interface would complicate the optimizer code, which is difficult enough to maintain as it is. Part of the reason PostgreSQL works as well as it does running queries is because feel-good code ("we can check off hinting on our
One of the ugly parts of Linux with PostgreSQL is that the OS will
happily cache up to around 5% of memory before getting aggressive about
writing it out. I've just updated a long list of pgbench runs showing how badly
that can turn out, even on a server with a modest 16GB of RAM. Note that I am intentionally trying to introduce the bad situation here, so this is not typical performance. The workload that pgbench generates is not representative of any real-world workload, it's as write-intensive as it's possible to be.Check
out test set 5, which is running a stock development version PostgreSQL 9.1. Some the
pauses where the database is unresponsive during checkpoints, as shown
by the max_latency figure there (which is in milliseconds), regularly
exceed 40 seconds.&
One of the more useful bits of
PostgreSQL documentation I ever worked on is Tuning Your PostgreSQL
Server. When that was written in the summer of 2008, a few months after the
release of PostgreSQL 8.3, it was hard to find any similar guide that
was both (relatively) concise and current. Since then, myself and
many other PostgreSQL contributors have helped keep that document up
to date as changes to PostgreSQL were made.
The interesting and helpful trend
during that period is that parameters keep disappearing from the set
of ones you need to worry about. In PostgreSQL 8.2, there was a long
list of parameters you likely needed to adjust for good performance
on a PostgreSQL server: shared_buffers, effective_cache_size,
checkpoint_segments, autovacuum, max_fsm_pages,