On Fri, 7 Mar 2008, Pavel Rotek wrote:
well, this will be the main problem... But... do uncomitted trasactions affect toast space?
I think the demonstrated answer to this is yes.
(begin tx, load previous log, do business action, append new log, flush, do business action, append new log, flush, ... do business action, append new log, flush, commit tx).
If all you're doing is appending to the end of the log, why don't you make each "append" a new row in a table. Instead of building massive rows, use the database for what it was designed for, and have many smaller independent rows.
Matthew -- "To err is human; to really louse things up requires root privileges." -- Alexander Pope, slightly paraphrased -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance