controlling memory management with regard to a specific query (or groups of connections)

From: Jonathan Vanasco <postgres(at)2xlp(dot)com>
To: PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: controlling memory management with regard to a specific query (or groups of connections)
Date: 2015-11-19 01:10:00
Message-ID: 70B71B25-DE3F-46F3-832A-E3D27486C8FB@2xlp.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

As a temporary fix I need to write some uploaded image files to PostgreSQL until a task server can read/process/delete them.

The problem I've run into (via server load tests that model our production environment), is that these read/writes end up pushing the indexes used by other queries out of memory -- causing them to be re-read from disk. These files can be anywhere from 200k to 5MB.

has anyone dealt with situations like this before and has any suggestions? I could use a dedicated db connection if that would introduce any options.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Roxanne Reid-Bennett 2015-11-19 07:26:55 Re: controlling memory management with regard to a specific query (or groups of connections)
Previous Message Chris Richards 2015-11-19 00:31:15 What could cause CREATE TEMP... "could not read block" error?