Re: suggestion for backup (pg_dump)
Yes, It is useful. But situation is different. Most of the times objects
are first created, tested and only after finalization can go in the
extension update file. Also it can be difficult not to get the object
definitions from an extension in the backup from pg_dump. A customer could
have to execute commands to create and update extensions for all versions
to current. It can be very difficult.
My suggestion to provide an extra option for pg_dump to include objects of
specific types only along with switch for a schema.
Thanks for help. Looking out if it is really possible to use extension for
our software.
Regards,
C P Kulkarni
On Sun, May 20, 2012 at 12:43 PM, Gabriele Bartolini <
gabriele.bartolini@2ndquadrant.it> wrote:
Show quoted text
Hi,
Il 19/05/12 19:09, c k ha scritto:
similar tasks and already using it. This problem arises when I have to
issue an update script to the client having only function mostly. And as
most of the functions are dependent on others and having more than 1100
functions it becomes hard to write a list of objects for pg_dump.It may sound unrelated at first, but if you have PostgreSQL 9.1 this use
case matches very well with the new EXTENSION framework. Please look at the
CREATE EXTENSION command and evaluate it.Cheers,
Gabriele--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gabriele.bartolini@**2ndQuadrant.it | www.2ndQuadrant.it