Skip site navigation (1) Skip section navigation (2)

Re: [QUESTIONS] postgresql-6.3 and jdbc - grief

From: "Stephan B(dot) Doliov" <doliov(at)statsol(dot)com>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: [QUESTIONS] postgresql-6.3 and jdbc - grief
Date: 1998-03-13 23:04:32
Message-ID: Pine.GSO.3.96.980313145456.18448A-100000@shell (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
Pter Mount wrote:
> On Fri, 13 Mar 1998, Stephan B. Doliov wrote:
> > I know i must be doing something inanely stupid but the jdbc driver that
> > 
> > in pg_hba.conf i have
> > local      all  password password
> > host       all   password password
> This is your problem, the IP address & mask don't match (for postgresql's
> purposes).
> If you are trying to say: only is to have access, then it
> should read:
> host       all   password password
> but, if you are saying that the network that resides is to
> have access, and is the netmask, then this should read:

thanks for clarifying my consfusion regarding netmasks (i just did an
ifconfig -a on my le0 (ethernet) interface and saw the netmask ws
ffffffe0) and so thought that is what i should put in the pg_hba.conf

however - the mystery i still have not yet been able to solve is why do i
have to speccify the host in the url in order to get the jdbc driver to
jdbc:postgresql:funnystuff fails
jdbc:postgresql:// works.

pg_hba.conf reads:
local   all    password      password
host    all   password   password

is it because poastmaster is running with the -i option?  if i let the
pg_hba.conf file for local read
local   all   trust
i don't need to specify the hostname in the url.

by and large, i can live with this no problem, it's just that my curiosity
has been greatly aroused by the observed behavior.



pgsql-interfaces by date

Next:From: Constantin TeodorescuDate: 1998-03-14 12:23:54
Subject: Re: [INTERFACES] pgaccess: I can't save a view
Previous:From: Stephan B. DoliovDate: 1998-03-13 20:20:05

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group