Re: PostgreSQL as a local in-memory cache

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "jgardner@xxxxxxxxxxxxxxxxxxx" <jgardner@xxxxxxxxxxxxxxxxxxx>, pgsql-performance@xxxxxxxxxxxxxx
Subject: Re: PostgreSQL as a local in-memory cache
From: "Pierre C" <lists@xxxxxxxxxx>
Date: Wed, 16 Jun 2010 09:51:14 +0200
In-reply-to: <4634b12c-749f-4605-9d95-121b8e2bd9e4@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <cb0fb58c-9134-4314-a1d0-08fc39f911a6@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <87bpbcpabg.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4C17A417.2040600@xxxxxxxx> <87ocfcnqmk.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4C180A3B.7090905@xxxxxxxxxxxx> <4634b12c-749f-4605-9d95-121b8e2bd9e4@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Opera Mail/10.10 (Linux)

Have you tried connecting using a UNIX socket instead of a TCP socket onlocalhost ? On such very short queries, the TCP overhead is significant.


--
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

Follow-Ups:
- Re: PostgreSQL as a local in-memory cache
  - From: Jonathan Gardner

References:
- PostgreSQL as a local in-memory cache
  - From: jgardner@xxxxxxxxxxxxxxxxxxx
- Re: PostgreSQL as a local in-memory cache
  - From: Chris Browne
- Re: PostgreSQL as a local in-memory cache
  - From: Steve Wampler
- Re: PostgreSQL as a local in-memory cache
  - From: Chris Browne
- Re: PostgreSQL as a local in-memory cache
  - From: Josh Berkus
- Re: PostgreSQL as a local in-memory cache
  - From: jgardner@xxxxxxxxxxxxxxxxxxx

Prev by Date: Re: PostgreSQL as a local in-memory cache
Next by Date: Re: PostgreSQL as a local in-memory cache
Previous by thread: Re: PostgreSQL as a local in-memory cache
Next by thread: Re: PostgreSQL as a local in-memory cache
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]