Question

尝试从Web应用程序连接到PostGres数据库时，它不起作用。

使用psql从终端尝试时，确实如此。

我做错了什么？

pgconnect3.js测试脚本：

var pg = require('pg');
var winston = require('winston');
var conString="postgres://postgres:test123test@localhost:5432/uaa_client";
winston.level = 'debug';

pg.connect(conString, function(err, client, done) {
  if(err) {
    winston.debug('Error connecting to Postgres');
    winston.debug('err', err);
    return 1;
  } else {
    winston.debug("Successfully connected");
    client.query("SELECT * FROM uaa_client", function(err, result){
      done();
      if(err) {
        winston.error('Error reading from Postgres');
        return 1;
      }
      else{
        winston.info('Results: ', result);
      }
    });
  }
});

它重现的错误：

$ node pgconnect3.js 
debug: Error connecting to Postgres
debug: err error: database "uaa_client" does not exist
    at Connection.parseE (/Users/patricklunney/Sites/testing/node_modules/pg/lib/connection.js:554:11)
    at Connection.parseMessage (/Users/patricklunney/Sites/testing/node_modules/pg/lib/connection.js:381:17)
    at Socket.<anonymous> (/Users/patricklunney/Sites/testing/node_modules/pg/lib/connection.js:117:22)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at readableAddChunk (_stream_readable.js:146:16)
    at Socket.Readable.push (_stream_readable.js:110:10)
    at TCP.onread (net.js:523:20)

好的，所以人们可能认为数据库不存在。没那么快。

$ psql -h localhost -p 5432 -U postgres -W -d uaa_client
Password for user postgres: 
psql (9.5.2, server 9.5.3)
Type "help" for help.

uaa_client=#

是什么给出的？我可以在psql中连接到uaa_client，并且在pgAdmin3中也是可见的。

Here is a pic of pgAdmin3

pg_hba.conf文件：

# PostgreSQL Client Authentication Configuration File
# ===================================================
#
# Refer to the "Client Authentication" section in the PostgreSQL
# documentation for a complete description of this file.  A short
# synopsis follows.
#
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access.  Records take one of these forms:
#
# local      DATABASE  USER  METHOD  [OPTIONS]
# host       DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
# hostssl    DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
# hostnossl  DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
#
# (The uppercase items must be replaced by actual values.)
#
# The first field is the connection type: "local" is a Unix-domain
# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
# plain TCP/IP socket.
#
# DATABASE can be "all", "sameuser", "samerole", "replication", a
# database name, or a comma-separated list thereof. The "all"
# keyword does not match "replication". Access to replication
# must be enabled in a separate record (see example below).
#
# USER can be "all", a user name, a group name prefixed with "+", or a
# comma-separated list thereof.  In both the DATABASE and USER fields
# you can also write a file name prefixed with "@" to include names
# from a separate file.
#
# ADDRESS specifies the set of hosts the record matches.  It can be a
# host name, or it is made up of an IP address and a CIDR mask that is
# an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
# specifies the number of significant bits in the mask.  A host name
# that starts with a dot (.) matches a suffix of the actual host name.
# Alternatively, you can write an IP address and netmask in separate
# columns to specify the set of hosts.  Instead of a CIDR-address, you
# can write "samehost" to match any of the server's own IP addresses,
# or "samenet" to match any address in any subnet that the server is
# directly connected to.
#
# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi",
# "ident", "peer", "pam", "ldap", "radius" or "cert".  Note that
# "password" sends passwords in clear text; "md5" is preferred since
# it sends encrypted passwords.
#
# OPTIONS are a set of options for the authentication in the format
# NAME=VALUE.  The available options depend on the different
# authentication methods -- refer to the "Client Authentication"
# section in the documentation for a list of which options are
# available for which authentication methods.
#
# Database and user names containing spaces, commas, quotes and other
# special characters must be quoted.  Quoting one of the keywords
# "all", "sameuser", "samerole" or "replication" makes the name lose
# its special character, and just match a database or username with
# that name.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal.  If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect.  You can
# use "pg_ctl reload" to do that.

# Put your actual configuration here
# ----------------------------------
#
# If you want to allow non-local connections, you need to add more
# "host" records.  In that case you will also need to make PostgreSQL
# listen on a non-local interface via the listen_addresses
# configuration parameter, or via the -i or -h command line switches.

# CAUTION: Configuring the system for local "trust" authentication
# allows any local user to connect as any PostgreSQL user, including
# the database superuser.  If you do not trust all your local users,
# use another authentication method.


# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
local   all             all                                     trust
# IPv4 local connections:
host    all             all             127.0.0.1/32            trust
# IPv6 local connections:
host    all             all             ::1/128                 trust
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication     postgres                                trust
#host    replication     postgres        127.0.0.1/32            trust
#host    replication     postgres        ::1/128                 trust

Answer 1

可能是pg_hba.conf中的设置打开Postgresql中的日志记录，它可能会告诉你更多

pg.connect无法正常工作，但psql适用于本地postgres db。我究竟做错了什么？

1 个答案: