Douglas McNaught <[EMAIL PROTECTED]> writes:
> You could also enforce use of the
> private network (in both cases) by use of firewall rules.
I think the real point here is that any additional security you gain
comes from having the physically separate wire. It's foolish to suppose
that using a no
[EMAIL PROTECTED] writes:
> Hi John,
>
> Unix sockets are a presentation layer interface to TCP/IP. You're not
> avoiding it by using them.
That's not true. Unix sockets are fundamentally different and do not
use TCP/IP at all. They have their own namespace (in the Unix
filesystem) and go thro
Hi John,
Unix sockets are a presentation layer interface to TCP/IP. You're not
avoiding it by using them.
Rick
"John Zubac"
<[EMAIL PROTECTED]
"John Zubac" <[EMAIL PROTECTED]> writes:
> Hi Everyone
>
> I am not too sure how to do this but I'll ask
>
> I want two postgres servers to communicate over a serial port. I want to
> avoid using the TCP/IP network protocol for added security. I heard this
> can be accomplished through unix socket
Title: FW: Configuring Postgres to use unix sockets
Hi Everyone
I am not too sure how to do this but I'll ask
I want two postgres servers to communicate over a serial port. I want to avoid using the TCP/IP network protocol for added security. I heard this can be accomplished through unix
