Re: Errno checks for rmtree()

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: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Errno checks for rmtree()
Date: 2005-02-13 01:23:56
Message-ID: 200502130123.j1D1Nud27581@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > + static void
> > + rmtree_errno(char *filepath)
> > + {
> > + if (errno == EACCES)
> > + #ifndef FRONTEND
> > + elog(LOG, "no permission to remove \"%s\"", filepath);
> > + #else
> > + fprintf(stderr, "no permission to remove \"%s\"", filepath);
> > + #endif
> > + else if (errno == EBUSY)
> > [ etc ]
>
> This seems awfully bogus: it's incomplete and not in the style of our
> other error messages. Why not just one case:
>
> #ifndef FRONTEND
> elog(LOG, "could not remove \"%s\": %m", filepath);
> #else
> fprintf(stderr, "could not remove \"%s\": %s\n", filepath,
> strerror(errno));
> #endif

OK, so you just wanted _an_ error string to be printed on failure rather
than the reasons.

> Also, I'm unconvinced that LOG is the appropriate error level;
> WARNING would probably be better.

Yea, good point.

--
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-patches by date

  From Date Subject
Next Message Tom Lane 2005-02-13 01:26:05 Re: Errno checks for rmtree()
Previous Message Tom Lane 2005-02-13 00:59:13 Re: Errno checks for rmtree()