| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: drop if exists remainder |
| Date: | 2006-02-07 02:22:34 |
| Message-ID: | 43E8046A.7030108@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
>>> Here's a first draft patch for DROP ... IF EXISTS for the remaining
>>> cases, namely: LANGUAGE, TABLESPACE, TRIGGER OPERATOR CLASS,
>>> FUNCTION, AGGREGATE, OPERATOR, CAST and RULE.
>>>
>>
>> At what point does this stop being useful and become mere bloat?
>> The only case I can ever recall being actually asked for was the
>> TABLE case ...
>
> Chris KL said it should be done for all on the grounds of consistency.
> But I will happily stop right now if that's not the general view - I'm
> only doing this to complete something I started.
Well, my use-case was to be able to wrap "pg_dump -c" output in
begin/commit tags and being able to run and re-run such dumps without
errors. Basically I don't like 'acceptable errors' when restoring dumps
:) They just confuse newer users especially.
I also just like consistency :)
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2006-02-07 02:24:31 | Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and |
| Previous Message | Bruce Momjian | 2006-02-07 02:08:08 | Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-02-07 02:26:57 | Re: drop if exists remainder |
| Previous Message | Bruce Momjian | 2006-02-07 01:40:18 | Re: [BUGS] BUG #2171: Differences compiling plpgsql in |