File:PGDay2010-Extensions.pdf

From PostgreSQL wiki

(PostgreSQL extensibility is remarkable but incomplete. It lacks dump and restore support. What that means is that once an extension is installed into your database, PostgreSQL currently has no idea of what SQL objects belongs to the extension rather itself, so the dump will contain the instructions to install the extension. That's only practical if you want to restore your dump targeting the very same extension's version, but when upgrading systems that's seldom what happens. This talk will detail how to fix this problem and more, explaining you how to benefit from the extensions capabilities for your own work within the database.)

Latest revision as of 20:53, 8 December 2010

PostgreSQL extensibility is remarkable but incomplete. It lacks dump and
restore support. What that means is that once an extension is installed
into your database, PostgreSQL currently has no idea of what SQL objects
belongs to the extension rather itself, so the dump will contain the
instructions to install the extension. That's only practical if you want
to restore your dump targeting the very same extension's version, but
when upgrading systems that's seldom what happens. This talk will detail
how to fix this problem and more, explaining you how to benefit from the
extensions capabilities for your own work within the database.

File history

PostgreSQL extensibility is remarkable but incomplete. It lacks dump and restore support. What that means is that once an extension is installed into your database, PostgreSQL currently has no idea of what SQL objects belongs to the extension rather itself, so the dump will contain the instructions to install the extension. That's only practical if you want to restore your dump targeting the very same extension's version, but when upgrading systems that's seldom what happens. This talk will detail how to fix this problem and more, explaining you how to benefit from the extensions capabilities for your own work within the database.