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

From: Jonathan Vanasco <jvanasco(at)2xlp(dot)com>
To: Roxanne Reid-Bennett <rox(at)tara-lu(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: controlling memory management with regard to a specific query (or groups of connections)
Date: 2015-11-19 15:55:56
Message-ID: 9093950E-67BF-489D-9B9D-BE170DD59C55@2xlp.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Thanks. Unfortunately, this is in a clustered environment. NFS and other shared drive systems won't scale well. I'd need to run a service that can serve/delete the local files, which is why I'm just stashing it in Postgres for now.

> On Nov 19, 2015, at 2:26 AM, Roxanne Reid-Bennett <rox(at)tara-lu(dot)com> wrote:
>
> We have a system that loads a bunch of files up to be processed - we queue them for processing behind the scenes. We don't load them into Postgres before processing. We put them in a temp directory and just save the location of the file to the database. This configuration does have limitations. Post-processing can not be load balanced across servers unless the temp directory is shared.
>
> I'm sure you'll get more DB centric answers from others on the list.
>
> Roxanne

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2015-11-19 16:05:35 Re: postgres zeroization of dead tuples ? i.e scrubbing dead tuples with sensitive data.
Previous Message Day, David 2015-11-19 15:47:57 Re: postgres zeroization of dead tuples ? i.e scrubbing dead tuples with sensitive data.