pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Martin Foster <martin@ethereal-realms.org>
To: Simon Riggs <simon@2ndquadrant.com>
To: pgsql-performance@postgresql.org
Subject: Re: Restricting Postgres
Date: Thu, 04 Nov 2004 08:17:22 -0500
Message-ID: <418A2BE2.70609@ethereal-realms.org> (raw)
In-Reply-To: <1099570740.4320.196.camel@localhost.localdomain>
References: <M4Vhd.85137$9b.34888@edtnps84>
	<1099509684.4320.2.camel@localhost.localdomain>
	<41894CD9.8090308@ethereal-realms.org>
	<1099570740.4320.196.camel@localhost.localdomain>

Simon Riggs wrote
> 
> 
> All workloads are not created equally, so mixing them can be tricky.
> This will be better in 8.0 because seq scans don't spoil the cache.
> 
> Apache is effectively able to segregate the workloads because each
> workload is "in a directory". SQL isn't stored anywhere for PostgreSQL
> to say "just those ones please", so defining which statements are in
> which workload is the tricky part.
> 
> PostgreSQL workload management could look at userid, tables, processor
> load (?) and estimated cost to decide what to do.
> 
> There is a TODO item on limiting numbers of connections per
> userid/group, in addition to the max number of sessions per server.
> 
> Perhaps the easiest way would be to have the Apache workloads segregated
> by PostgreSQL userid, then limit connections to each.
> 

Apache has a global setting for load average limits, the above was just 
a module which extended the capability.  It might also make sense to 
have limitations set on schema's which can be used in a similar way to 
Apache directories.

While for most people the database protecting itself against a sudden 
surge of high traffic would be undesirable.   It can help those who run 
dynamically driven sites and get slammed by Slashdot for example.

	Martin Foster
	Creator/Designer Ethereal Realms
	martin@ethereal-realms.org





view thread (34+ messages)  latest in thread

Message-ID: <418A2BE2.70609@ethereal-realms.org>
Permalink:  ../418A2BE2.70609@ethereal-realms.org/
Also on:    postgresql.org/message-id/418A2BE2.70609@ethereal-realms.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: martin@ethereal-realms.org, simon@2ndquadrant.com
  Subject: Re: Restricting Postgres
  In-Reply-To: <418A2BE2.70609@ethereal-realms.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox