ARGOMENTO: installazione

non vedo però una riga nel pg_hba.conf per quanto riguarda la connessione dalla rete locale.
quelle presenti riguardano socket e connessioni tcp locali.

nel mio file pg_hba.conf ho solo queste righe, hai per caso un esempio di una tua configurazione ?

# DO NOT DISABLE!
# If you change this first entry you will need to make sure that the
# database superuser can access the database using some other method.
# Noninteractive access to all databases is required during automatic
# maintenance (custom daily cronjobs, replication, and similar tasks).
#
# Database administrative login by Unix domain socket
local all postgres peer

# TYPE DATABASE USER ADDRESS METHOD
local all odoo md5

# "local" is for Unix domain socket connections only
local all all peer
# IPv4 local connections:
host all all 192.168.1.0 255.255.255.0 trust

# IPv6 local connections:
host all all ::1/128 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local replication postgres peer
#host replication postgres 192.168.1.0/24 md5
#host replication postgres ::1/128 md5

ho trovato questo esempio direttamente su www.postgresql.org/docs/9.3/static/auth-pg-hba-conf.html
mi viene un dubbio di tipo sistemistico...il mio router assegna al mio server l'IP 192.168.1.209 mentre al client 192.168.1.202
forse ho capito male, ma nei parametri quando viene indicato ad esempio

# TYPE DATABASE USER ADDRESS METHOD
host postgres all 192.168.93.0/24 ident

significa che accetta connessioni da macchine con indirizzo da 0 a 24 ? io ho provato pure ad aumentare il range, ma quando faccio ripartire il servizio postgresql mi da errore proprio su quella riga



# Allow any user on the local system to connect to any database with
# any database user name using Unix-domain sockets (the default for local
# connections).
#
# TYPE DATABASE USER ADDRESS METHOD
local all all trust

# The same using local loopback TCP/IP connections.
#
# TYPE DATABASE USER ADDRESS METHOD
host all all 127.0.0.1/32 trust

# The same as the previous line, but using a separate netmask column
#
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
host all all 127.0.0.1 255.255.255.255 trust

# The same over IPv6.
#
# TYPE DATABASE USER ADDRESS METHOD
host all all ::1/128 trust

# The same using a host name (would typically cover both IPv4 and IPv6).
#
# TYPE DATABASE USER ADDRESS METHOD
host all all localhost trust

# Allow any user from any host with IP address 192.168.93.x to connect
# to database "postgres" as the same user name that ident reports for
# the connection (typically the operating system user name).
#
# TYPE DATABASE USER ADDRESS METHOD
host postgres all 192.168.93.0/24 ident

# Allow any user from host 192.168.12.10 to connect to database
# "postgres" if the user's password is correctly supplied.
#
# TYPE DATABASE USER ADDRESS METHOD
host postgres all 192.168.12.10/32 md5

# Allow any user from hosts in the example.com domain to connect to
# any database if the user's password is correctly supplied.
#
# TYPE DATABASE USER ADDRESS METHOD
host all all .example.com md5

# In the absence of preceding "host" lines, these two lines will
# reject all connections from 192.168.54.1 (since that entry will be
# matched first), but allow Kerberos 5 connections from anywhere else
# on the Internet. The zero mask causes no bits of the host IP
# address to be considered, so it matches any host.
#
# TYPE DATABASE USER ADDRESS METHOD
host all all 192.168.54.1/32 reject
host all all 0.0.0.0/0 krb5

# Allow users from 192.168.x.x hosts to connect to any database, if
# they pass the ident check. If, for example, ident says the user is
# "bryanh" and he requests to connect as PostgreSQL user "guest1", the
# connection is allowed if there is an entry in pg_ident.conf for map
# "omicron" that says "bryanh" is allowed to connect as "guest1".
#
# TYPE DATABASE USER ADDRESS METHOD
host all all 192.168.0.0/16 ident map=omicron

# If these are the only three lines for local connections, they will
# allow local users to connect only to their own databases (databases
# with the same name as their database user name) except for administrators
# and members of role "support", who can connect to all databases. The file
# $PGDATA/admins contains a list of names of administrators. Passwords
# are required in all cases.
#
# TYPE DATABASE USER ADDRESS METHOD
local sameuser all md5
local all @admins md5
local all +support md5

# The last two lines above can be combined into a single line:
local all @admins,+support md5

# The database column can also use lists and file names:
local db1,db2,@demodbs all md5

RISOLTO...ma che fatica per un ragioniere come me

ho modificato le regole del router in modo che gli indirizzi IP partono da 192.168.1.2
ho reimpostato il pg_hba.conf com'era all'inizio senza la sbrodolata che suggerisce il sito di Postgresql
ho modificato il postgresql.conf aggiungendo la riga listen_addresses = '*'

dal client :

psql -h 192.168.1.2 -d DB_DEMO_IT -U postgres -W
Password for user postgres:
psql (9.3.5)
SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
Type "help" for help.

DB_DEMO_IT=#

ed ovviamente mi collego anche da PgAdmin3

mi sono arrangiato quasi da solo, ma grazie per il supporto morale e per non avermi mandato a f.....o pubblicamente