From: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
To: pgsql-performance@postgresql.org
Subject: Re: Restricting Postgres
Date: Thu, 04 Nov 2004 21:30:35 +0100
Message-ID: <opsgyi89iccq72hf@musicbox> (raw)
In-Reply-To: <003301c4c29a$f052d910$8300a8c0@solent>
References: <003301c4c29a$f052d910$8300a8c0@solent>
On Thu, 4 Nov 2004 18:20:18 -0000, Matt Clark <matt@ymogen.net> wrote:
>> Correct the 75% of all hits are on a script that can take
>> anywhere from
>> a few seconds to a half an hour to complete. The script
>> essentially
>> auto-flushes to the browser so they get new information as it arrives
>> creating the illusion of on demand generation.
Er, do you mean that :
1- You have a query that runs for half an hour and you spoon feed the
results to the client ?
(argh)
2- Your script looks for new data every few seconds, sends a packet, then
sleeps, and loops ?
If it's 2 I have a readymade solution for you, just ask.
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: lists@boutiquenumerique.com
Subject: Re: Restricting Postgres
In-Reply-To: <opsgyi89iccq72hf@musicbox>
* 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