pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Martin Foster <martin@ethereal-realms.org>
To: pgsql-performance@postgresql.org
Subject: Re: Restricting Postgres
Date: Fri, 05 Nov 2004 02:49:42 GMT
Message-ID: <aTBid.57485$E93.26193@clgrps12> (raw)
In-Reply-To: <418ABCD1.7020407@ymogen.net>
References: <003301c4c29a$f052d910$8300a8c0@solent>
	<opsgyi89iccq72hf@musicbox>
	<418A98C0.9010107@ymogen.net>
	<opsgyneoj4cq72hf@musicbox>
	<418AAF12.8030307@ymogen.net>
	<opsgyq6mj7cq72hf@musicbox>
	<418ABCD1.7020407@ymogen.net>

Matt Clark wrote:

> 
> 
> Pierre-Frédéric Caillaud wrote:
> 
>>
>> check this marvelus piece of 5 minutes of work :
>> http://boutiquenumerique.com/test/iframe_feed.html
>>
> cela m'a fait le sourire :-)
> 
> (apologies for bad french)
> 
> M
> 
> 

Javascript is not an option for the scripts, one of the mandates of the 
project is to support as many different client setups as possible and we 
have encountered everything from WebTV to the latest Firefox release. 
  It's a chat/roleplay community and not everyone will invest in new 
equipment.

Now, it would seem to me that there is a trade off between a JS push 
system and a constant ever-present process.    With the traditional 
method as I use it, a client will incur the initial penalty of going 
through authentication, pulling the look and feel of the realms, sites 
and simply poll one table from that point on.

Now on the other hand, you have one user making a call for new posts 
every x amount of seconds.   This means every X seconds the penalty for 
authentication and design would kick in, increasing overall the load.

The current scripts can also by dynamically adapted to slow things down 
based on heavy load or quiet realms that bring little posts in.   It's 
much harder to expect Javascript solutions to work perfectly every time 
and not be modified by some proxy.

Unfortunately, we are getting way off track.   I'm looking for a way to 
protect the PostgreSQL server, either from PostgreSQL or some sort of 
external script which pools load average once in a while to make that 
determination.

Now is there an administrative command in PostgreSQL that will cause it 
to move into some sort of maintenance mode?   For me that could be 
exceedingly useful as it would still allow for an admin connection to be 
made and run a VACUUM FULL and such.

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



view thread (34+ messages)  latest in thread

Message-ID: <aTBid.57485$E93.26193@clgrps12>
Permalink:  ../aTBid.57485$E93.26193@clgrps12/
Also on:    postgresql.org/message-id/aTBid.57485$E93.26193@clgrps12

 · 

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
  Subject: Re: Restricting Postgres
  In-Reply-To: <aTBid.57485$E93.26193@clgrps12>

* 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