December archive
Psycopg 2.3.2 released
Posted by Daniele Varrazzo
on December 20, 2010
Tagged as
news,
release
Hello,
just released Psycopg 2.3.2. The release fixes a bug reported in 2.3.0 and 2.3.1 preventing Psycopg to connect to pgBouncer. Thanks to Marti Raudsepp for the bug report and the patch.
Psycopg 2.3.1 released
Posted by Daniele Varrazzo
on December 4, 2010
Tagged as
news,
release
Hello,
just released Psycopg 2.3.1. No new feature since release 2.3.0: the only fix is for a build issue on CentOS 5.5 x86_64 (ticket #23).
Psycopg 2.3.0 released
Posted by Federico Di Gregorio
on December 1, 2010
Tagged as
news,
release
Hi *,
lately my involvment on psycopg has been quite small (work and other projects are taking their toll) but thanks to Daniele (with some help from Jan) here is a new psycopg2 release. The number of changes is big (an excerpt from the NEWS file is at the end, as always) so we decided to bump up the version to 2.3.0 and to test, and test... and test. We tested this new release on Linux and Windows, with Python 2.4, 2.5, 2.6, 2.7 and on PostgreSQL from 7.4 to 9.0.
PostgreSQL notifications with Psycopg2 and Eventlet
Posted by Daniele Varrazzo
on December 1, 2010
Tagged as
async,
eventlet,
notify,
recipe
PostgreSQL supports asynchronous notifications, a simple messaging system allowing clients to be notified about events occurred in the database. Notifications can be sent by any session using a "NOTIFY channel" command and will be received by any session which has subscribed with a LISTEN channel to receive updates. The system has been greatly improved in PostgreSQL 9.0 with the addition of a message payload, making the feature even more useful. Previously a typical use case would have been to notify interested sessions that a certain table was updated: now it is possible to signal for instance which record was changed. You can put the NOTIFY command in a database trigger for automatic notifications on insert or update... the possibilities are actually quite interesting.