Skip site navigation (1) Skip section navigation (2)

Re: scale up (postgresql vs mssql)

From: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
To: Claudio Freire <klaussfreire(at)gmail(dot)com>
Cc: Eyal Wilde <eyal(at)impactsoft(dot)co(dot)il>, pgsql-performance(at)postgresql(dot)org
Subject: Re: scale up (postgresql vs mssql)
Date: 2012-04-13 17:49:07
Message-ID: 4F886713.5020306@pinpointresearch.com (view raw or flat)
Thread:
Lists: pgsql-performance
On 04/13/2012 09:43 AM, Claudio Freire wrote:
> On Fri, Apr 13, 2012 at 1:36 PM, Steve Crawford
> <scrawford(at)pinpointresearch(dot)com>  wrote:
>> If they are permanent tables used for temporary storage then making them
>> unlogged may be beneficial. But actual temporary tables *are* unlogged and
>> attempting to create an unlogged temporary table will raise an error.
> Interesting, yes, I was wondering why PG didn't make temp tables
> unlogged by default.
>
> Then, I guess, the docs[0] have to mention it. Especially due to the
> error condition. Right?
>
> [0] http://www.postgresql.org/docs/9.1/static/sql-createtable.html
>
Well, the fact that temporary and unlogged cannot be simultaneously 
specified *is* documented:

CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF 
NOT EXISTS ] table_name

But it would probably be worth adding a note under the description of 
temporary tables that they are, in fact, unlogged.

Cheers,
Steve


In response to

Responses

pgsql-performance by date

Next:From: Claudio FreireDate: 2012-04-13 17:52:45
Subject: Re: scale up (postgresql vs mssql)
Previous:From: Tomas VondraDate: 2012-04-13 17:09:10
Subject: Re: PostgreSQL - Help Optimizing performance - full text search on Heroku

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group