From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
---|---|
To: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: synchronous_standby_name format |
Date: | 2017-07-14 16:34:56 |
Message-ID: | CABzCKRDsEvDcHYJ_YvbwyxvFEU5WJ78dCNqgzVb1ZUnKJw+7NA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Sorry, I should have better explained this. I was trying to build the
application_name using the server's FQDN, and yes, I tried various forms of
quoting the name to no avail. The real issue here though arose from trying
to configure this using ansible. I was just trying to add a new replica
using a new plaubook without defining a lot a variables.
On Jul 14, 2017 11:56 AM, "Jerry Sievers" <gsievers19(at)comcast(dot)net> wrote:
> John Scalia <jayknowsunix(at)gmail(dot)com> writes:
>
> > Hi all,
> >
> > I've been asked to make our setup a little more secure. So, I thought
> > I would restrict which servers could replicate from our primary.
> > However, it does not appear that 9.6.3 can use a FQDN entry for this
> > parameter. Plus, our hostnames include "-" characters, and that seems
> > to break the system as well. Shouldn't synchronous_standby_names
> > accept a FQDN with a dot or a dash in the hostname or is this maybe a
> > bug? (Flame suit on)
>
> HBA file is where you restrict access based on IP/netmask or DNS names.
>
> synchronous_standby_names has nothing whatsoever to do with this.
>
> HTH
>
> > --
> > Jay
> >
> >
>
> --
> Jerry Sievers
> Postgres DBA/Development Consulting
> e: postgres(dot)consulting(at)comcast(dot)net
> p: 312.241.7800
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Boiko | 2017-07-17 16:07:38 | web pgadmin API |
Previous Message | Jerry Sievers | 2017-07-14 15:56:33 | Re: synchronous_standby_name format |