Sorry for misspelling your name. It is almost midnight here...
So Dear Alvaro, [is it ok? :)]
This table is updated (not inserted... just updated) by another server in
every minutes. The procedure creates a few (configurable number of) empty
minutes in advance as a placeholder for the coming measured values. If there
are no empty minute records the value is lost.
If the db server is off for a long time, the minutes must be created
backwards too to avoid the holes. This situation is where many thousands of
records must be inserted at once.
I hope it was clear.
Cheers
-- Csaba
-----Original Message-----
From: Alvaro Herrera [mailto:alvherre@dcc.uchile.cl]
Sent: Thursday, December 23, 2004 11:12 PM
To: Együd Csaba (Freemail)
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Very slow stored proc
On Thu, Dec 23, 2004 at 09:48:56PM +0100, Együd Csaba (Freemail) wrote:
Hi,
> Dear Alvarao,
Wow, now that's a strange misspelling. I've seen several but this one is
new to me :-D
> would you please so kind explaining me your opinion in details.
What do you want that table for? If you are using it as input for a query,
it's possible that you can forget about refilling it every now and then, and
instead using a set-returning function (SRF) in the FROM clause of said
query.
--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>) "I dream about dreams about
dreams", sang the nightingale under the pale moon (Sandman)
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.298 / Virus Database: 265.6.4 - Release Date: 2004.12.22.
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.298 / Virus Database: 265.6.4 - Release Date: 2004.12.22.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.298 / Virus Database: 265.6.4 - Release Date: 2004.12.22.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.298 / Virus Database: 265.6.4 - Release Date: 2004.12.22.
