8.0.X will have proper filename reporting for rmtree() failures.
---
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> [ looks at code... ] dbcommands.c is expecting that rmtree() will have
> >> printed out
Bruce Momjian writes:
> Tom Lane wrote:
>> It's certainly not realistic to pass back enough information from
>> rmtree() to let the caller print a useful error message, so I think
>> we have to add reporting code along this line to rmtree().
> Agreed. Not sure how the rmtree stuff was removed.
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> [ looks at code... ] dbcommands.c is expecting that rmtree() will have
> >> printed out a more-detailed message about the problem, but someone has
> >> carefully removed every trace of error reporting from rmtree().
>
> > I think t
Bruce Momjian writes:
> Tom Lane wrote:
>> [ looks at code... ] dbcommands.c is expecting that rmtree() will have
>> printed out a more-detailed message about the problem, but someone has
>> carefully removed every trace of error reporting from rmtree().
> I think the issue is that we didn't wan
Tom Lane wrote:
> =?ISO-8859-15?Q?Hubert_Fr=F6hlich?= <[EMAIL PROTECTED]> writes:
> > dropdb ax20050206
> > WARNING: could not remove database directory
> > "/export/home/postgres/data2/base/115101837"
> > DROP DATABASE
>
> That's not very helpful, is it?
>
> [ looks at code... ] dbcommands.c
=?ISO-8859-15?Q?Hubert_Fr=F6hlich?= <[EMAIL PROTECTED]> writes:
> dropdb ax20050206
> WARNING: could not remove database directory
> "/export/home/postgres/data2/base/115101837"
> DROP DATABASE
That's not very helpful, is it?
[ looks at code... ] dbcommands.c is expecting that rmtree() will ha
