On 10/4/22 12:33, Alvaro Herrera wrote:
On 2022-Oct-04, Ron wrote:
Sometimes (both interactively and via script) I access a remote Pg server
via just the bare host name "foobar", and other times via the FQDN
"foobar.example.com".
I've only been able to get this to work by having two lines in t
On Tue, Oct 4, 2022 at 1:02 PM Ron wrote:
>
> Sometimes (both interactively and via script) I access a remote Pg server
> via just the bare host name "foobar", and other times via the FQDN
> "foobar.example.com".
>
> I've only been able to get this to work by having two lines in the .pgpass
> fil
On 10/4/22 10:02 AM, Ron wrote:
Sometimes (both interactively and via script) I access a remote Pg
server via just the bare host name "foobar", and other times via the
FQDN "foobar.example.com".
I've only been able to get this to work by having two lines in the
.pgpass file:
foobar:5432:p
On 2022-Oct-04, Ron wrote:
> Sometimes (both interactively and via script) I access a remote Pg server
> via just the bare host name "foobar", and other times via the FQDN
> "foobar.example.com".
>
> I've only been able to get this to work by having two lines in the .pgpass
> file:
Maybe it wou
Sometimes (both interactively and via script) I access a remote Pg server
via just the bare host name "foobar", and other times via the FQDN
"foobar.example.com".
I've only been able to get this to work by having two lines in the .pgpass file:
foobar:5432:postgres:Allegedly.Strong.Password
