pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Kris Jurka <books@ejurka.com>
Cc: Jim C. Nasby <jnasby@pervasive.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-patches@postgresql.org
Subject: Re: [PERFORM] WAL logging of SELECT ... INTO command
Date: Wed, 26 Apr 2006 19:02:34 -0400 (EDT)
Message-ID: <200604262302.k3QN2YW23329@candle.pha.pa.us> (raw)
In-Reply-To: <Pine.BSO.4.63.0603241308130.14309@leary.csoft.net>


Backpatched to 8.0.X and 8.1.X.

---------------------------------------------------------------------------

Kris Jurka wrote:
> 
> 
> 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

Content-Description: 

[ Attachment, skipping... ]

Content-Description: 

[ Attachment, skipping... ]

> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

-- 
  Bruce Momjian   http://candle.pha.pa.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +



view thread (21+ messages)

Message-ID: <200604262302.k3QN2YW23329@candle.pha.pa.us>
Permalink:  ../200604262302.k3QN2YW23329@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200604262302.k3QN2YW23329@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: pgman@candle.pha.pa.us, books@ejurka.com, jnasby@pervasive.com, simon@2ndquadrant.com, pgsql-patches@postgresql.org
  Subject: Re: [PERFORM] WAL logging of SELECT ... INTO command
  In-Reply-To: <200604262302.k3QN2YW23329@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox