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

Re: [PERFORM] WAL logging of SELECT ... INTO command

From: Kris Jurka <books(at)ejurka(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-performance(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org
Subject: Re: [PERFORM] WAL logging of SELECT ... INTO command
Date: 2006-03-24 18:09:26
Message-ID: Pine.BSO.4.63.0603241308130.14309@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-patchespgsql-performance

On Fri, 24 Mar 2006, Jim C. Nasby wrote:

> On Wed, Mar 22, 2006 at 02:37:28PM -0500, Kris Jurka wrote:
>>
>> On Wed, 22 Mar 2006, Jim C. Nasby wrote:
>>
>>> Ok, I saw disk activity on the base directory and assumed it was pg_xlog
>>> stuff. Turns out that both SELECT INTO and CREATE TABLE AS ignore
>>> default_tablepsace and create the new tables in the base directory. I'm
>>> guessing that's a bug... (this is on 8.1.2, btw).
>>
>> This has been fixed in CVS HEAD as part of a patch to allow additional
>> options to CREATE TABLE AS.
>>
>> http://archives.postgresql.org/pgsql-patches/2006-02/msg00211.php
>
> I'll argue that the current behavior is still a bug and should be fixed.
> Would it be difficult to patch 8.1 (and 8.0 if there were tablespaces
> then...) to honor default_tablespace?

Here are patches that fix this for 8.0 and 8.1.

Kris Jurka

Attachment: ctas_default_tablespace_81.patch
Description: text/plain (1.9 KB)
Attachment: ctas_default_tablespace_80.patch
Description: text/plain (1.9 KB)

In response to

Responses

pgsql-performance by date

Next:From: Chris BrowneDate: 2006-03-24 18:21:23
Subject: Re: Scaling up PostgreSQL in Multiple CPU / Dual Core
Previous:From: Scott MarloweDate: 2006-03-24 16:42:58
Subject: Re: Postmaster using only 4-5% CPU

pgsql-patches by date

Next:From: Simon RiggsDate: 2006-03-25 10:52:10
Subject: Re: Where does the time go?
Previous:From: Jim C. NasbyDate: 2006-03-24 13:59:46
Subject: Re: WAL logging of SELECT ... INTO command

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