| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ToDo: pg_backup - using a conditional DROP |
| Date: | 2011-11-15 14:30:05 |
| Message-ID: | CAFj8pRA2uu8zDu19gZJSY0vQRbnZjZiRGCE7fp5JEF9hAKydig@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2011/11/15 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> 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.
>
> That is not going to be possible unless we commit to having an IF EXISTS
> option for every type of DROP statement, now and in the future.
> Even then, it's not apparent to me that it solves any real use-case.
> You're probably better off just using --clean and ignoring any errors.
>
ook
Regards
Pavel Stehule
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2011-11-15 14:39:18 | Re: Disable OpenSSL compression |
| Previous Message | Tom Lane | 2011-11-15 14:17:59 | Re: Regression tests fail once XID counter exceeds 2 billion |