On 08.08.2012, at 22:04, Merlin Moncure wrote:
> What is the general structure of the procedure? In particular, how
> are you browsing and updating the rows?
Here it is -
BEGIN
for statistics_row in SELECT * FROM statistics ORDER BY time ASC
LOOP
...
... here some very minimal transformation is done
... and the row is written into the second table
...
END LOOP;
RETURN 1;
END;
> There is (almost) no way to
> force commit inside a function --
So what you are saying is that this behavior is normal and we should either equip ourselves with enough disk space (which I am trying now, it is a cloud server, which I am resizing to gain more disk space and see what will happen) or do it with an external (scripting) language?
> there has been some discussion about
> stored procedure and/or autonomous transaction feature in terms of
> getting there.
>
> I say 'almost' because you can emulate some aspects of autonomous
> transactions with dblink, but that may not be a very good fit for your
> particular case.
I met already dblink mention in this context somewhere... Though if plpgsql performs well with more disk space, I'll leave it for now. It is a one time operation this one.
Thank you,
Geert
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
