From: Wei Tjioe <wtjioe@cs.toronto.edu>
To: Fernando Nasser <fnasser@redhat.com>
Cc: rhdb@sources.redhat.com
Subject: Re: problem with Configuring a Connection to a Database using Visual Explain
Date: Thu, 02 Oct 2003 22:44:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.58.0310021756550.3485@qew.cs> (raw)
In-Reply-To: <3F7C94E5.8040807@redhat.com>
Thanks for the response. I just want to report these observations in case
someone experience the same connection failure.
Here's the environment where the said behavior of pgaccess and Visual
Explain in my last posting were observed:
(note: same applies with *local* commented out in pg_hba.conf)
in postgresql.conf, we have:
----------------------------------------------------
# Connection Parameters
#
#tcpip_socket = false
tcpip_socket = true
#ssl = false
ssl = true
#max_connections = 32
#port = 5432
#hostname_lookup = false
#show_source_port = false
#unix_socket_directory = ''
#unix_socket_group = ''
#unix_socket_permissions = 0777
_________________________________________________________
in pg_hba.conf, we have:
------------------------------------------------------
# host
# ----
#
# This record identifies networked hosts that are permitted to connect
# via IP connections.
#
# Format:
#
# host DBNAME IP_ADDRESS ADDRESS_MASK AUTH_TYPE [AUTH_ARGUMENT]
#...
#local all md5
host all 127.0.0.1 255.255.255.255 md5
_______________________________________________________________
> And were you connecting from the same machine?
The Visual Explain (and pgaccess) client is running in the same machine as
the postmaster server. I assumed tcpip sockets, rather than unix sockets,
would be used when configured as above.
>
>
> This uses Unix sockets, so it is no good for comparison.
Does this mean Unix Sockets were used even when 'Host' is explicitly
specified in Visual Explain -> configure ..., and when no local connection
is configured in pg_hba.conf?
I am also under the impression that pgaccess uses tpcip connection when a
host is explicitly specified (left non-blank) during a connection request.
Visual Explain and pgaccess are reading the exact same configuration
files, and using the exact same connection parameters:
Database:
Host:
Port:
User Name:
Password:
Wei
next prev parent reply other threads:[~2003-10-02 22:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 1:39 Wei Tjioe
2003-10-02 20:07 ` Fernando Nasser
2003-10-02 20:28 ` Wei Tjioe
2003-10-02 21:13 ` Fernando Nasser
2003-10-02 22:44 ` Wei Tjioe [this message]
2003-10-03 0:41 ` Fernando Nasser
2003-10-03 1:16 ` Wei Tjioe
2003-10-03 1:53 ` Fernando Nasser
2003-10-03 2:21 ` Wei Tjioe
-- strict thread matches above, loose matches on Subject: below --
2003-09-18 8:25 huwang wang
2003-09-18 14:36 ` Patrick Macdonald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.58.0310021756550.3485@qew.cs \
--to=wtjioe@cs.toronto.edu \
--cc=fnasser@redhat.com \
--cc=rhdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).