Tom Lane wrote:
>"Andrew Dunstan" <andrew@dunslane.net> writes:
>
>
>>Both of these are not always correct - they might well have configured a
>>listening address but we were unable to bind to it, although in that case
>>a warning would have already been issued. To be strictly correct either we
>>need to use a flag to distinguish the these cases, or we need an error
>>message that contemplates both cases.
>>
>>
>
>How about "no socket created for listening" or some such?
>
>
>
That works.
cheers
andrew