| From: | Adriaan van Os <postgres(at)microbizz(dot)nl> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: insert vs select into performance |
| Date: | 2007-07-18 19:28:40 |
| Message-ID: | 469E69E8.3080204@microbizz.nl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Michael Stone wrote:
> On Tue, Jul 17, 2007 at 10:58:01PM +0200, Thomas Finneid wrote:
>> I am not sure I understand you correctly here, are you saying that
>> SELECT INTO in 8.1 disables WAL logging and uses just a single fsync
>> at the end? in that case it means that I could disable WAL as well and
>> achieve the same performance, does it not?
>
> Yes. The difference is that the select into optimization just means that
> if the system crashes the data you're inserting is invalid (and is
> properly cleaned up), and disabling the WAL means that if the system
> crashes everything is invalid (and can't be cleaned up).
So, how does one (temporarily) disable WAL logging ? Or, for example, disable WAL logging for a
temporary table ?
Regards,
Adriaan van Os
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-07-18 19:58:02 | Re: insert vs select into performance |
| Previous Message | Thomas Finneid | 2007-07-18 19:24:18 | Re: improvement suggestions for performance design |