https://blog.pgxn.org/tags/build/Build2011-09-08T06:39:00ZThe PGXN MaintainersHugohttps://blog.pgxn.org/post/9950473714PGXN Utils 0.1.3 Released!2026-10-07T16:13:48Z2011-09-08T06:39:00ZDickson S. GuedesHello 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.

]]>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: https://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!

]]>https://blog.pgxn.org/post/6883009649PGXN Utils 0.1.2 Released!2026-10-07T16:13:48Z2011-06-24T23:53:00ZDickson S. GuedesHello everyone!

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

Now you can release a distribution to PGXN in five steps!

First, install it:

gem install pgxn_utils

Second, create your extension, optionally overwrite some defaults:

mkdir $HOME/extensions
cd $HOME/extensions
pgxn_utils skeleton my_extension --maintainer "Dickson S. Guedes"

Third, code!

Fourth, bundle it:

pgxn_utils bundle my_extension
Extension generated at: /home/guedes/extensions/my_extension-0.0.1.zip

Fifth, release it:

pgxn_utils release my_extension-0.0.1.zip
Enter your PGXN username: guedes
Enter your PGXN password: ******
Trying to release my_cool_extension-0.0.1.zip ... released successfully!
Visit: https://manager.pgxn.org/distributions/my_cool_extension/0.0.1

Ah, you can export PGXN_USER and PGXN_PASSWORD if you are tired to type your username and password every time.

]]>Hello everyone!

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

Now you can release a distribution to PGXN in five steps!

First, install it:

gem install pgxn_utils

Second, create your extension, optionally overwrite some defaults:

mkdir $HOME/extensions
cd $HOME/extensions
pgxn_utils skeleton my_extension --maintainer "Dickson S. Guedes"

Third, code!

Fourth, bundle it:

pgxn_utils bundle my_extension
Extension generated at: /home/guedes/extensions/my_extension-0.0.1.zip

Fifth, release it:

pgxn_utils release my_extension-0.0.1.zip
Enter your PGXN username: guedes
Enter your PGXN password: ******
Trying to release my_cool_extension-0.0.1.zip ... released successfully!
Visit: https://manager.pgxn.org/distributions/my_cool_extension/0.0.1

Ah, you can export PGXN_USER and PGXN_PASSWORD if you are tired to type your username and password every time.

Check this out!.

]]>https://blog.pgxn.org/post/5758832725PGXN Utils 0.1.1 Released!2026-10-07T16:13:48Z2011-05-23T04:53:30ZDickson S. GuedesHello everyone!

This was a productive weekend that allowed me to work on some new features in pgxn_utils and I’m proud to tell you that a new version was released!

Trying to simplify your extension-development life I’ve added two tasks to pgxn_utils: change and bundle. The first one is just a convenient way to change META information about extension, incrementally, the second one is an easy way to archive your extension in a zip file well named.

]]>Hello everyone!

This was a productive weekend that allowed me to work on some new features in pgxn_utils and I’m proud to tell you that a new version was released!

Trying to simplify your extension-development life I’ve added two tasks to pgxn_utils: change and bundle. The first one is just a convenient way to change META information about extension, incrementally, the second one is an easy way to archive your extension in a zip file well named.

To install it just type:

gem install pgxn_utils

Or, if you don’t want to install it yet, see it in action on this screencast 3:05.

Work in progress…

I’m working now to simplify the release, creating a task to send bundled file to PGXN.

There are a lot of work to do yet so, please, tell me if you found a bug or have suggestions.

Have a nice code! “:)

]]>https://blog.pgxn.org/post/5465631144PGXN Utils2026-10-07T16:13:48Z2011-05-14T01:05:00ZDickson S. GuedesDo you ever have problems with copy and paste? I often did, and that is why I create custom templates for often used files that match certain patterns.

With files from the structure of PostgreSQL’s extensions was the same thing.

I was tired of creating the files and edit the META, controlfile, READMEs, etc. every time I start a new extension and felt that I need something that made me more productive, so I decided to create an automatic generator and share it with the world.

]]>Do you ever have problems with copy and paste? I often did, and that is why I create custom templates for often used files that match certain patterns.

With files from the structure of PostgreSQL’s extensions was the same thing.

I was tired of creating the files and edit the META, controlfile, READMEs, etc. every time I start a new extension and felt that I need something that made me more productive, so I decided to create an automatic generator and share it with the world.

I called it pgxn-utils, and you should give it a try: it is easy to install, easy to use and will help you to start hacking quickly!

How?

  1. First install it:

    gem install pgxn_utils

  2. Then start a new extension:

    pgxn_utils skeleton my_cool_extension

Thats all! It will create the initial skeleton for you and you can start coding! But, if you don’t want to install it, see it in action

Good hack!

]]>https://blog.pgxn.org/post/5458118596New HOWTO2026-10-07T16:13:48Z2011-05-13T20:34:46ZDavid E. WheelerI updated the howto yesterday. This document explains how to create a PGXN distribution. If you’re interested in releasing PostgreSQL extensions on PGXN, this document is worth a read.

In essence, it’s really simple: Just create a META.json and upload. But to get the full benefit, there are quite a few other recommendations. Already familiar with it? Here’s the checklist:

  • Create a META.json
  • Create a control file
  • Create a Makefile
  • Implement the code in the sql and src directories
  • Write tests in the test directory
  • Write a Text::Markup-recognizable README
  • Write Text::Markup-recognizable documentation in the doc directory
  • Consider including other files: Changes, LICENSE, INSTALL, COPYING, AUTHORS
  • Release it!

Be sure to read the howto for details. Got feedback or suggestions? Leave a comment!

]]>I updated the howto yesterday. This document explains how to create a PGXN distribution. If you’re interested in releasing PostgreSQL extensions on PGXN, this document is worth a read.

In essence, it’s really simple: Just create a META.json and upload. But to get the full benefit, there are quite a few other recommendations. Already familiar with it? Here’s the checklist:

  • Create a META.json
  • Create a control file
  • Create a Makefile
  • Implement the code in the sql and src directories
  • Write tests in the test directory
  • Write a Text::Markup-recognizable README
  • Write Text::Markup-recognizable documentation in the doc directory
  • Consider including other files: Changes, LICENSE, INSTALL, COPYING, AUTHORS
  • Release it!

Be sure to read the howto for details. Got feedback or suggestions? Leave a comment!

Oh, and check out pgxn-utils and simplify your extension-development life.

]]>