[rt-users] Making "make initdb" idempotent?

Craig Ringer craig at 2ndquadrant.com
Mon Jun 24 03:13:36 EDT 2013

On 06/21/2013 11:56 PM, Ruslan Zakirov wrote:
> On Fri, Jun 21, 2013 at 5:36 PM, Craig Ringer <craig at 2ndquadrant.com
> <mailto:craig at 2ndquadrant.com>> wrote:
>     On 06/21/2013 08:21 PM, Ruslan Zakirov wrote:
>     > Hi,
>     >
>     > Some of what you mention may be partially implemented in a branch
>     > (upgrade history). Note that "Don't create if it exists" concept
>     is not
>     > something we're targeting at. Our approach is to register upgrade
>     files
>     > so they can not be applied twice so easy.
>     >
>     Hm. That'd work if an extension could provide multiple upgrade files, so
>     each new version could add new upgrade files.
> Our extensions do this. Each version that needs DB upgrade provides a
> separate upgrade dir with schema, content... like RT itself.

OK, that sounds interesting. Are there any docs on this? The RT
extensions I've looked into, like RT::Extension::SLA, don't seem to use
this mechanism.

Are you talking about a new facility that's added as part of the branch
you describe, or something supported in mainline?

 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

More information about the rt-users mailing list