pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Barnard <kevin.barnard@gmail.com>
To: Martin Foster <martin@ethereal-realms.org>
Cc: PostgreSQL <pgsql-general@postgresql.org>
Subject: Re: [PERFORM] Restricting Postgres
Date: Thu, 4 Nov 2004 10:00:38 -0600
Message-ID: <b068057c041104080051ccc451@mail.gmail.com> (raw)
In-Reply-To: <418A2BE2.70609@ethereal-realms.org>
References: <M4Vhd.85137$9b.34888@edtnps84>
	<1099509684.4320.2.camel@localhost.localdomain>
	<41894CD9.8090308@ethereal-realms.org>
	<1099570740.4320.196.camel@localhost.localdomain>
	<418A2BE2.70609@ethereal-realms.org>

I am generally interested in a good solution for this.  So far our
solution has been to increase the hardware to the point of allowing
800 connections to the DB.

I don't have the mod loaded for Apache, but we haven't had too many
problems there.  The site is split pretty good between dynamic and
non-dynamic, it's largely Flash with several plugins to the DB. 
However we still can and have been slammed and up to point of the 800
connections.

What I don't get is why not use pgpool?  This should eliminate the
rapid fire forking of postgres instanaces in the DB server.  I'm
assuming you app can safely handle a failure to connect to the DB
(i.e. exceed number of DB connections).  If not it should be fairly
simple to send a 503 header when it's unable to get the connection.

On Thu, 04 Nov 2004 08:17:22 -0500, Martin Foster
<martin@ethereal-realms.org> wrote:
> 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
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>



view thread (34+ messages)  latest in thread

Message-ID: <b068057c041104080051ccc451@mail.gmail.com>
Permalink:  ../b068057c041104080051ccc451@mail.gmail.com/
Also on:    postgresql.org/message-id/b068057c041104080051ccc451@mail.gmail.com

 · 

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: kevin.barnard@gmail.com, martin@ethereal-realms.org, pgsql-general@postgresql.org
  Subject: Re: [PERFORM] Restricting Postgres
  In-Reply-To: <b068057c041104080051ccc451@mail.gmail.com>

* 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