PostgreSQL Query Cache - "pqc"

I would like to introduce a new open source software, PostgreSQL Query Cache, which enables to improve query performance extremely (10x~100x) by caching query results in front of backends.

PostgreSQL Query Cache:

• waits connections on the different port from the clients.
• delegates queries in front of the backends, like a proxy.
• intercepts and caches SELECT query results.
• also manages lifecycle of the query cache.

5 steps to implement a PostgreSQL replication system

Yesterday, I tried to build a PostgreSQL master-slave replication system with new feature "Streaming Replication (SR)", which is coming in the next PostgreSQL major release 9.0 as a built-in replication solution, and it worked well on my servers.

I feel it is very easy to configure, so I have decided to make some memos here for building a PostgreSQL master-slave replication system.

Here are 5 steps to implement a PostgreSQL replication system.

1. Build and install binaries.
2. Initialize a database cluster and duplicate it.
3. Configure the master node.
4. Configure the slave node(s).
5. Start the master and slave node(s).

Ok, let's start.

(This photo was taken at the PostgreSQL 9 TestFest Japan.)

PostgreSQL 9 TestFest Japan on Apr.4

Some Japanese PostgreSQL developers are inspired by the SFPUG’s TestFest announce, and we are now planning to have our TestFest at 3am-10am Apr.4 in Tokyo/Japan, which is equivalent to 11am-6pm Apr.3 PST in SanFrancisco.

PostgreSQL 9 is going to be a very exciting release, and we hope to try many new things around PostgreSQL 9. So we have decided to have our TestFest as an all-night event, like a hackathon.

PostgreSQL Cluster: “Too Many Projects” problem

“Too Many Projects” problem

The “too many projects” problem of PostgreSQL Cluster was raised and discussed in the PostgreSQL Clustering Developer Meeting at the JPUG Conference.

Nowadays, the PostgreSQL developer community has many clustering/replication projects, but many of them are not production ready. Though, new project is starting, and old project is still unmature.

I think this is one of the biggest challenges of the OpenSource development community.

Why happens this? How can we solve this, and get solutions mature?

Back to the OpenSource world

Finally, I’m back to the OpenSource world.

In 2004, I started working as a PostgreSQL developer and database engineer. While I was working as a PostgreSQL engineer, I was joining several PostgreSQL cluster projects, including Slony-II. Unfortunately, some were not happen, but it gave me great experiences.

At the same time, I was working as a director of Japan PostgreSQL Users Group (JPUG), and planned and run several community events such as JPUG conferences, camps and study groups. I was enjoying meeting with technical and non-technical people around PostgreSQL in Japan.

After a few years working as a PostgreSQL engineer, I moved to the datacenter business division in Oct.2007, and started working as a business developer of the datacenter services. It was very exciting to look for the market in the datacenter and cloud boom.