We've been a bit quiet on the postgres.js front lately, but there's a couple of exciting new announcements that we'd like to go over with Postgres.js
Firstly, we've plugged in LISTEN/NOTIFY support. This is huge, as it allows you to register asynchronous callbacks based on events from Postgres, outside of any transactional context.
Additionally, as of PG 9.0, NOTIFY messages from the Postgres server can contain an arbitrary text payload. …
Blog
PgEast 2011: NYC Call for papers
December 16th, 2010: Celebrating 15 years of PostgreSQL, early.
Following on the smashing success of PostgreSQL Conference West, PostgreSQL Conference West, The PostgreSQL Conference for Developers, End Users and Decision Makers, is being held at the Hotel Pennsylvania, in New York City from March 22nd through 25th 2011. Please join us in continuing to make this the largest PostgreSQL Conference series!
- PostgreSQL Conference
- Call for papers
Thank you to our …
R.I.P. PostgreSQL (Mammoth) Replicator
In 2004, PostgreSQL Core Team member Josh Berkus wrote[1]:
"Slony-I is undoubtedly our most popular replication tool. It supports Master-Slave High Availability Replication. However, there are a number of other solutions, such as dbMirror, eRServer, pgPool, C-JDBC, and the proprietary Mammoth Replicator, all of which are in wide use because they solve different replication problems than Slony-I does. Replication is not a single solution for a single problem; it is …
Looking for an Intermediate Sysadmin + Junior DBA
Command Prompt, Inc. is looking for an intermediate systems administrator and junior PostgreSQL administrator.
Command Prompt has provided PostgreSQL support, development, and hosting since 1997. We are looking for another person to join our stellar group of PostgreSQL systems experts.
We seek someone who has a deep knowledge of at least one UNIX-like system, and who knows how to manage heterogeneous systems well. You can demonstrate strong skills in basic …
Automatically pulling into a committer's Git repository
I was a bit unhappy because I couldn't keep my "bare" Git repository up-to-date unattended — I needed to be at my workstation to be able to do a git fetch, because it needs my SSH passphrase.
I didn't have this problem with CVS because I kept an rsync copy of the anonymous CVS repository, from which my regular trees where checked out. (My committer's checkouts were separate, which …
Fixing foreign key deadlocks, part 2 revisited
While trying to implement SELECT FOR KEY LOCK at the lock manager level, I stumbled across the problem that I need to represent the lock faithfully in the lock manager's terms. And since I previously mentioned that FOR KEY LOCK would conflict with FOR SHARE, I get in trouble — it's not easy to see which lock mode to use (if there is one, which I doubt).
So I …
Fixing foreign key deadlocks, part 2
In the previous article, I explained the problem with foreign key checks checks obtaining too strong of a lock, and promised that we would be attempting to fix it.
Here is my proposal:
- Create a new SELECT locking clause. For now, we're calling it SELECT FOR KEY LOCK
- This will acquire a new type of lock in the tuple, dubbed a "keylock".
- This lock will conflict with DELETE, …
Fixing foreign key deadlocks
I've been commissioned to work on foreign keys. More specifically, on the problem that when foreign keys are verified, they sometimes obtain locks that are stronger than really needed. This causes some operations to block unnecessarily and, perhaps more aggravating, some other operations to deadlock.
This problem has been known for a very long time, and it affects many users to varying degrees. The most recent detailed discussion about this …
Node and Postgres
Or, two great tastes that work together.
PostgreSQL Conference West was last week, and we will be looking at East 2011 in a few short months. I was fortunate enough to present a paper on Postgres.js, the driver I've been working on for Node.js for the past several months.
I had a lot of great feedback in my talk, a lot of great questions, and even some immediate bug reports. …
Replication Poll results
Back before PostgreSQL Conference West, there was a poll. That poll was replication. Here are the results. There were 367 respondents. Have fun with it!
| Q | responses | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | In what waydo you use PostgreSQL? | |||||||||
| Development Only | 72 | |||||||||
| As a hobby (or personaldevelopment) | 106 | |||||||||
| Professionally | 325 | |||||||||
| 2 | What versionof PostgreSQL are you running? | |||||||||
| 8.3 | 117 | |||||||||
| 9.0 | 175 | |||||||||
| 8.2 | 50 | |||||||||
| 8.1 | 36 | |||||||||
| 8.4 | 251 | |||||||||
| 3 | Do you use or plan to use … | |||||||||