Re: BUG #5680: Failure to start: too many private dirs demanded - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5680: Failure to start: too many private dirs demanded
Date
Msg-id 249.1285711833@sss.pgh.pa.us
Whole thread Raw
In response to BUG #5680: Failure to start: too many private dirs demanded  ("Alexey Parshin" <alexeyp@gmail.com>)
List pgsql-bugs
Alexey Parshin <alexeyp@gmail.com> writes:
> And then found a link /usr/share/zoneinfo/Australia/Australia to
> /usr/share/zoneinfo/Australia/Australia. Clearly, this isn't PostgreSQL
> fault. Removing that link solved it. Thanks a lot.

Ah-hah.

> A simple suggestion that would help in diagnostics: A message like 'too many
> dir entries demanded' is more useful if the path in question is shown. For
> example, a message like:

> *Too many dir entries demanded. The path is
> "/usr/share/zoneinfo/Australia/Australia/Australia/Australia/Eucla"*

Hmm, not sure this sort of thing has ever come up before.  But certainly
we can expend a couple more bytes on that error message.  Done in HEAD.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5681: Using set returning function as subrequest can result losing rows in result set
Next
From: Alexey Parshin
Date:
Subject: Re: BUG #5680: Failure to start: too many private dirs demanded