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
On Wed, Nov 18, 2015 at 5:10 PM, Jonathan Vanasco wrote:
> 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
>
On Wed, 18 Nov 2015 20:10:00 -0500
Jonathan Vanasco wrote:
> 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
>
On 11/19/2015 12:29 PM, Bill Moran wrote:
On Wed, 18 Nov 2015 20:10:00 -0500
Jonathan Vanasco wrote:
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
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
On 11/18/2015 5:10 PM, Jonathan Vanasco wrote:
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