Re: [GENERAL] WARNING: could not remove database directory

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hubert Fröhlich <hubert(dot)froehlich(at)bvv(dot)bayern(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] WARNING: could not remove database directory
Date: 2005-02-11 18:29:54
Message-ID: 200502111829.j1BITsi18842@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Tom Lane wrote:
> =?ISO-8859-15?Q?Hubert_Fr=F6hlich?= <hubert(dot)froehlich(at)bvv(dot)bayern(dot)de> 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 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 want different object files for
client and server output message and and returning error codes and
having every calling location print strings was unmaintainable.

Seems we never got a solution to that.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-02-11 18:36:21 Re: [GENERAL] WARNING: could not remove database directory
Previous Message Mark Harrison 2005-02-11 18:20:47 size in bytes of a table?

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-02-11 18:36:21 Re: [GENERAL] WARNING: could not remove database directory
Previous Message Tom Lane 2005-02-11 17:18:40 Re: passing parameters by reference