| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | WAL logging of SELECT ... INTO command |
| Date: | 2006-03-21 12:22:11 |
| Message-ID: | 20060321122211.GU15742@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches pgsql-performance |
Currently, it appears that SELECT * INTO new_table FROM old_table logs
each page as it's written to WAL. Is this actually needed? Couldn't the
database simply log that the SELECT ... INTO statement was executed
instead? Doing so would likely result in a large performance improvement
in most installs. Is there no provision for writing anything but data
page changes (or whole pages) to WAL?
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-03-21 13:38:27 | Re: fix of some issues with multi-line query editing |
| Previous Message | Bruce Momjian | 2006-03-21 03:41:59 | Re: FW: Win32 unicode vs ICU |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Hayward | 2006-03-21 12:22:31 | Re: Best OS & Configuration for Dual Xeon w/4GB & Adaptec |
| Previous Message | Jim C. Nasby | 2006-03-21 12:18:39 | Re: Migration study, step 1: bulk write performance |