Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 5B8AD133655C for ; Wed, 27 Oct 2010 23:01:15 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 10283-02 for ; Thu, 28 Oct 2010 02:01:08 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-iw0-f174.google.com (mail-iw0-f174.google.com [209.85.214.174]) by mail.postgresql.org (Postfix) with ESMTP id DABE9133616B for ; Wed, 27 Oct 2010 23:01:07 -0300 (ADT) Received: by iwn10 with SMTP id 10so1752254iwn.19 for ; Wed, 27 Oct 2010 19:01:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=j0DhzhgFqeXnig7B20MV/MPS+eeSLeTwA9sycyE5fgo=; b=coHZDHRRSwQdnGjMrvrl8jJlbG9DpAQ2KZ28AhyvkSq+cL7ruH0/16C49NRgz8Zif1 WnxCpaNavcTJlU3AkiAtM19cDfR7eXMzEE4OaqR8E/29ejVX6ZUrX5dv1pKfbzMVajAv 9RDPdlBhiuIkX9I6N1x294WWqHSWH3tfOqdbM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=r2AfcIYn/8UoDol+O/p0j/hcPxhqz3YJrfsn5l99reqaiNCE10vDcUDE0Es/rogEfl HaMyIgV7xasCEEQJc7ojclejTP7TLo85r/g6Rx3VVRmsWr4ZDJfqfS/7Xac+zsIk45Px cUJ2R8zMqsn5nskNOJIzcUm6LJy+GMGyXxRnA= MIME-Version: 1.0 Received: by 10.231.183.136 with SMTP id cg8mr2881913ibb.114.1288231267543; Wed, 27 Oct 2010 19:01:07 -0700 (PDT) Received: by 10.231.33.71 with HTTP; Wed, 27 Oct 2010 19:01:07 -0700 (PDT) In-Reply-To: References: <402913.53404.qm@web65405.mail.ac4.yahoo.com> <208728.42197.qm@web65409.mail.ac4.yahoo.com> <770715.39613.qm@web29003.mail.ird.yahoo.com> Date: Wed, 27 Oct 2010 22:01:07 -0400 Message-ID: Subject: Re: Re: Postgres insert performance and storage requirement compared to Oracle From: Robert Haas To: Ivan Voras Cc: pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201010/524 X-Sequence-Number: 40942 On Wed, Oct 27, 2010 at 6:13 AM, Ivan Voras wrote: > On 10/26/10 17:41, Merlin Moncure wrote: >> On Tue, Oct 26, 2010 at 11:08 AM, Leonardo Francalanci wrote: >>>> temp =A0tables are not wal logged or >>>> synced. =A0Periodically they can be flushed =A0to a permanent table. >>> >>> >>> What do you mean with "Periodically they can be flushed =A0to >>> a permanent table"? Just doing >>> >>> insert into tabb select * from temptable >>> >> >> yup, that's exactly what I mean -- this will give you more uniform > > In effect, when so much data is in temporary storage, a better option > would be to simply configure "synchronous_commit =3D off" (better in the > sense that the application would not need to be changed). The effects > are almost the same - in both cases transactions might be lost but the > database will survive. Gee, I wonder if it would possible for PG to automatically do an asynchronous commit of any transaction which touches only temp tables. --=20 Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company