| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
| Cc: | kadams(at)mxlogic(dot)com, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: WAL log performance/efficiency question |
| Date: | 2007-05-17 14:55:52 |
| Message-ID: | 25796.1179413752@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Heikki Linnakangas <heikki(at)enterprisedb(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Keaton Adams | 2007-05-17 15:34:43 | Re: WAL log performance/efficiency question |
| Previous Message | Heikki Linnakangas | 2007-05-17 14:23:00 | Re: WAL log performance/efficiency question |