From: | Torello Querci <tquerci(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ToDo: pg_backup - using a conditional DROP |
Date: | 2011-11-15 09:31:23 |
Message-ID: | CA+igE6TvsXw3vhXnu5gptDv9=PFa_z0jC=xXJXZqVUeTUq6P=A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2011/11/15 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> Hello,
>
> there is a request on enhancing of pg_backup to produce a conditional
> DROPs. A reason for this request is more simple usage in very dynamic
> production - cloud BI solution.
>
> pg_backup can have a new option "--conditional-drops" and then pg_dump
> will produce a DROP IF EXISTS statements instead DROP statements.
>
> Ideas, comments?
>
I think that if there is other way to get the same result in other way
is better to use it without add new options.
In this case, if you are on unix environment, I suppose that you can
use external batch to manipulate the output file, like "sed" I
suppose.
Obviusly this is my personal opinion.
Best Regards
Torello
> Regards
>
> Pavel Stehule
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Kohei KaiGai | 2011-11-15 09:43:54 | Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement |
Previous Message | Pavel Stehule | 2011-11-15 08:05:45 | ToDo: pg_backup - using a conditional DROP |