Re: PGACCESS connection failure?

If you just want to connect over domain sockets, leave the "Host"
entry box blank in the "Open" database dialog.  I wouldn't have tried
until Iavor put the question the way he did.  Thanks!

--Chris

On Tue, 30 Jul 2002, Iavor Raytchev waxed:

> Hello William,
>
> I did not want to be impolite or something :) I am just hunting all
> issues that prevent people form using pgaccess as what I notice is that
> many people do not send bugs or requests simply because first of all
> they can not make it run.
>
> In this line it was important to know if you have anything against
> running PostgreSQL with '-i'. Thank you very much for your reply - it
> was very helpful and a good feedback.
>
> I hope the Unix Domain sockets question will be answered soon.
>
> All best,
>
> Iavor
>
> > -----Original Message-----
> > From: William West [mailto:wwest@csc.com]
> > Sent: Dienstag, 30. Juli 2002 01:06
> > To: Iavor Raytchev
> > Cc: pgsql-interfaces@postgresql.org; Preston Lord; pgaccess -
> > developers
> > Subject: Re: [INTERFACES] PGACCESS connection failure?
> >
> > '-i' works fine for me. I did not use it at first because I
> > did not know
> > that pgaccess needed it.
> >
> > Was only trying to be helpful to Preston. I have no particular reason
> > to be disturbed by pgaccess needing TCP/IP ... I just figured that
> > my TCL/TK did not have any Unix Domain support, and find it
> > acceptable to enable TCP/IP when needing the services of
> > pgaccess.
> >
> > It sounded like Preston's "BUT ..." could be the same thing I
> > ran into, needing to configure with '-i' when I did not expect to
> > need to do that, so I posted what I posted.
> >
> > But since you asked ... IS there a way to configure pgaccess
> > to use Unix Domain sockets?.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

-- 

cmaj_at_freedomcorpse_dot_info
0xC0051F6A
5EB8 2035 F07B 3B09 5A31  7C09 196F 4126 C005 1F6A