Re: TCP Overhead on Local Loopback

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Andy <angelflow(at)yahoo(dot)com>, Ofer Israeli <oferi(at)checkpoint(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: TCP Overhead on Local Loopback
Date: 2012-04-02 00:29:35
Message-ID: CAGTBQpZfvX7LznT35+WFQMZKUMuogqDFRLnky3BWRUz9-bFVRg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Sun, Apr 1, 2012 at 8:54 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> You could try using Unix domain socket and see if the performance
>> improves. A relevant link:
>
>
> He said Windows. There are no Unix domain sockets on Windows. (And please
> don't top-post)

Windows supports named pipes, which are functionally similar, but I
don't think pg supports them.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Andrew Dunstan 2012-04-02 01:11:03 Re: TCP Overhead on Local Loopback
Previous Message Andrew Dunstan 2012-04-01 23:54:39 Re: TCP Overhead on Local Loopback