PGXN Manager will be back up as soon as your DNS records update. All the PGXN sites are on their new server.

manager.pgxn.org will be doing down for the move to the new server in 10 minutes. #WishMeLuck

PGXN Manager will be going down for the move to the new server this evening. Stay tuned for details!

Anyone interested in building RPMs and/or Debian packages for the various parts of the PGXN infrastruture?

New server fell through, unfortunately. Will be looking for a new home for PGXN this week.

By Daniele Varrazzo

Finally, here it is. Well tested, documented, and pampered. With the PGXN Client installing extensions from the PGXN Network is a breeze:

$ pgxn install semver
$ pgxn load semver
$ psql
=# select 'foo'::semver;
ERROR:  bad semver value 'foo': expected number at foo
LINE 1: select 'foo'::semver;

Error! Meaning: success!

The number of extensions on PGXN is steadily increasing, so we hope the client will make their adoption even easier.

The client is now extensible: either writing in Python to reuse some of the other commands implementation or writing new self-contained scripts in any language to be invoked by the pgxn commands dispatcher. The first client extensions are already available: PGXN Utils and PGXN:Meta:Validator are targeted for easier development of new extensions.

The client is released on PyPI, so installing is just:

$ sudo easy_install pgxnclient

Complete documentation and further links are available from the project homepage.

Any feedback is welcome; you can contact me and all the other people behind PGXN on the PGXN User Group. See you there!

Thank you Jon Erdman for your donation! Your t-shirt is in the mail. #pgxn #fundraising

I’m off to Chicago today for Postgres Open, a new PostgreSQL conference. I’m pleased that I’ll be presenting “Get Your Preferred Feature Developed!”

There are lots of developers out there who, like me, have ideas for projects they want to work on for PostgreSQL, but don’t have the free time to make it happen. The idea for this talk is to pitch this fact to an audience of organizations with a major investment in PostgreSQL and an interest in seeing it improve. Perhaps one or more of them will look into sponsoring development of something that interests them, or that they need. This way, interested developers might get paid to work on projects that interest them, to the benefit of the project, the community, and of course their sponsors. Naturally, I’ll be drawing on PGXN as an example of how this sort of thing can work.

If you’e like to learn more, tune in! The whole conference will be live-streamed. Check the site on Wednesday to get hooked up.

by Dickson S. Guedes

Hello everyone!

I’m proud to tell you that a new version of pgxn_utils was released!

In this version some errors with OpenSSL was fixed (thanks @theory to report then), and now you can release an extension to PGXN in five steps even using Ruby 1.8!

Another change was the executable’s name that changed from pgxn_utils to pgxn-utils for a close integration with next version of PGXN Client, but some work need to be done, yet.

I used pgxn-utils to release itself to PGXN!

$ pgxn-utils release pgxn_utils-0.1.3.zip 
Enter your PGXN username: guedes
Enter your PGXN password: ***********************
Trying to release pgxn_utils-0.1.3.zip ... released successfully!
Visit: http://pgxn.org/dist/pgxn_utils/0.1.3/

Cool, eh? So, since the PGXN’s mirrors were synced and you have pgxn client, you could install pgxn_utils using:

pgxn install pgxn_utils

If you don’t have pgxn client you can install it using rubygems

gem install pgxn_utils

Have fun!

My presentation at the 2012 PDXPUG PGDay. It covers the basics of how to create useful extensions to PostgreSQL and distribute them on PGXN—without needing to learn C.