Thread

  1. pgpass hostname and IP address

    Ron Johnson <ron.l.johnson@cox.net> — 2018-03-10T04:19:15Z

    (8.4 and 9.2, but soon to 9.6)
    
    If we sometimes access a db server by IP address, and sometimes by hostname, 
    must we have two entries for each server+user (one with the hostname and the 
    other with IP address), or is there a way to put them both on the same line?
    
    -- 
    Angular momentum makes the world go 'round.
    
    
    
  2. Re: pgpass hostname and IP address

    David G. Johnston <david.g.johnston@gmail.com> — 2018-03-10T04:26:37Z

    On Friday, March 9, 2018, Ron Johnson <ron.l.johnson@cox.net> wrote:
    
    > (8.4 and 9.2, but soon to 9.6)
    >
    > If we sometimes access a db server by IP address, and sometimes by
    > hostname, must we have two entries for each server+user (one with the
    > hostname and the other with IP address), or is there a way to put them both
    > on the same lin
    >
    
     https://www.postgresql.org/docs/10/static/libpq-pgpass.html
    
    So unless you can make a wildcard work you are stuck with two separate
    lines.
    
    David J.
    
  3. Re: pgpass hostname and IP address

    Ron Johnson <ron.l.johnson@cox.net> — 2018-03-10T04:34:47Z

    On 03/09/2018 10:26 PM, David G. Johnston wrote:
    > On Friday, March 9, 2018, Ron Johnson <ron.l.johnson@cox.net 
    > <mailto:ron.l.johnson@cox.net>> wrote:
    >
    >     (8.4 and 9.2, but soon to 9.6)
    >
    >     If we sometimes access a db server by IP address, and sometimes by
    >     hostname, must we have two entries for each server+user (one with the
    >     hostname and the other with IP address), or is there a way to put them
    >     both on the same lin
    >
    >
    > https://www.postgresql.org/docs/10/static/libpq-pgpass.html
    >
    > So unless you can make a wildcard work you are stuck with two separate lines.
    
    Yeah, I read that (well, the ones for my ancient versions), but hoped there 
    might be something I missed, or some obscure and clever trick.
    
    -- 
    Angular momentum makes the world go 'round.
    
  4. Re: pgpass hostname and IP address

    Adrian Klaver <adrian.klaver@aklaver.com> — 2018-03-10T05:11:06Z

    On 03/09/2018 08:19 PM, Ron Johnson wrote:
    > (8.4 and 9.2, but soon to 9.6)
    > 
    > If we sometimes access a db server by IP address, and sometimes by 
    > hostname, must we have two entries for each server+user (one with the 
    > hostname and the other with IP address), or is there a way to put them 
    > both on the same line?
    > 
    
    Not with .pgpass, though there is the service file method:
    
    https://www.postgresql.org/docs/9.6/static/libpq-pgservice.html
    
    https://www.postgresql.org/docs/10/static/libpq-connect.html#LIBPQ-CONNSTRING
    
    service
    
         Service name to use for additional parameters. It specifies a 
    service name in pg_service.conf that holds additional connection 
    parameters. This allows applications to specify only a service name so 
    connection parameters can be centrally maintained. See Section 33.16.
    
    
    
    -- 
    Adrian Klaver
    adrian.klaver@aklaver.com
    
    
    
  5. Re: pgpass hostname and IP address

    Ron Johnson <ron.l.johnson@cox.net> — 2018-03-10T06:17:40Z

    On 03/09/2018 11:11 PM, Adrian Klaver wrote:
    > On 03/09/2018 08:19 PM, Ron Johnson wrote:
    >> (8.4 and 9.2, but soon to 9.6)
    >>
    >> If we sometimes access a db server by IP address, and sometimes by 
    >> hostname, must we have two entries for each server+user (one with the 
    >> hostname and the other with IP address), or is there a way to put them 
    >> both on the same line?
    >>
    >
    > Not with .pgpass, though there is the service file method:
    >
    > https://www.postgresql.org/docs/9.6/static/libpq-pgservice.html
    >
    > https://www.postgresql.org/docs/10/static/libpq-connect.html#LIBPQ-CONNSTRING
    >
    > service
    >
    >     Service name to use for additional parameters. It specifies a service 
    > name in pg_service.conf that holds additional connection parameters. This 
    > allows applications to specify only a service name so connection 
    > parameters can be centrally maintained. See Section 33.16.
    
    That looks promising.
    
    -- 
    Angular momentum makes the world go 'round.