Tom Lane wrote:
> "Andrew Dunstan" <[EMAIL PROTECTED]> 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?

Or "no socket available for listening"?

  Bruce Momjian                        |
  [EMAIL PROTECTED]               |  (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 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to