Anytime. Anywhere. Since 1997.
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:
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 …
| 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 … | |||||||||
Some days ago, I was reading some patch from the in-progress commitfest, and happened to notice this comment in src/include/tcopprot.h:
* This file was created so that other c files could get the two * function prototypes without having to include tcop.h which single * handedly includes the whole f*cking tree -- mer 5 Nov. 1991
The weird thing about this was that there's no tcop.h file on the …
Outside of Rob's points which I found valid (you can see it in the video) the one thing that bugged me is the aggressiveness of Facebook. It …
In the post, Josh Berkus makes the assertion, "50% of PGX's active clients have either already converted to 9.0 replication or have scheduled a conversion with us".
I have no doubts of Josh's statement but it brings up an interesting point when arguing about features in PostgreSQL. Josh's …