| From: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
|---|---|
| To: | Selena Deckelmann <selena(at)endpoint(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Sabino Mullane <greg(at)endpoint(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: One less footgun: deprecating pg_dump -d |
| Date: | 2009-03-09 19:14:34 |
| Message-ID: | 49B56A9A.3000204@cheapcomplexdevices.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Selena Deckelmann wrote:
> Tom Lane wrote:
>> Greg Sabino Mullane<greg(at)endpoint(dot)com> writes:
>>> ...
>>> deprecate -d by having it throw an exception when used.
>>
>> "Deprecate" does not mean "break".
> ...
> While this change may break existing scripts...less painful
Why do people want a failure rather than warning messages
being spewed to both stderr and the log files?
If someone doesn't notice warnings there, I wonder if
even throwing an exception would save them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-03-09 19:16:11 | Re: One less footgun: deprecating pg_dump -d |
| Previous Message | Magnus Hagander | 2009-03-09 19:12:39 | Re: One less footgun: deprecating pg_dump -d |