Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Keaton Adams wrote:
>> We are running on PostgreSQL 8.1.4 and are planning to move to 8.3 when
>> it becomes available. Are there space utilization/performance
>> improvements in WAL logging in the upcoming release?
> One big change in 8.3 is that COPY on a table that's been created or
> truncated in the same transaction doesn't need to write WAL at all, if
> WAL archiving isn't enabled.
There are a couple of improvements in tuple storage (the header is
shorter, and short varlena fields have less overhead); those would
translate pretty directly into less WAL space too.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
