| From: | Pierre-Frédéric Caillaud <lists(at)boutiquenumerique(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Restricting Postgres |
| Date: | 2004-11-04 20:30:35 |
| Message-ID: | opsgyi89iccq72hf@musicbox |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
On Thu, 4 Nov 2004 18:20:18 -0000, Matt Clark <matt(at)ymogen(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Edmund Bacon | 2004-11-04 20:34:33 | Re: disabling constraints |
| Previous Message | Martin Foster | 2004-11-04 20:30:19 | Re: Restricting Postgres |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-11-04 20:40:45 | Re: Anything to be gained from a 'Postgres Filesystem'? |
| Previous Message | Martin Foster | 2004-11-04 20:30:19 | Re: Restricting Postgres |