Bruce Momjian <pgman@candle.pha.pa.us> writes:
> OK, so you just wanted _an_ error string to be printed on failure rather
> than the reasons.

Well, what we want to know is the particular file that couldn't be
deleted and the errno code. This is all "can't happen" stuff and so
it just has to be a message that is useful for debugging; I don't see
that it has to be amazingly user-friendly.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > OK, so you just wanted _an_ error string to be printed on failure rather
> > than the reasons.
>
> Well, what we want to know is the particular file that couldn't be
> deleted and the errno code. This is all "can't happen" stuff and so
> it just has to be a message that is useful for debugging; I don't see
> that it has to be amazingly user-friendly.

Wow, you want to print out the raw errno number. We only do that in one
or two places in our code that I could fine.

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

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org