Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <sthomas@optionshouse.com>) id 1TPEAL-0001c3-FK
	for pgsql-performance@postgresql.org; Fri, 19 Oct 2012 15:07:13 +0000
Received: from smtp.peak6.com ([38.98.137.6])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <sthomas@optionshouse.com>) id 1TPEAF-0007OD-C9
	for pgsql-performance@postgresql.org; Fri, 19 Oct 2012 15:07:13 +0000
X-AuditID: 0a64cb1e-b7fd36d00000120f-a5-50816c8e3b5e
Message-ID: <50816C97.3060806@optionshouse.com>
Date: Fri, 19 Oct 2012 10:07:03 -0500
From: Shaun Thomas <sthomas@optionshouse.com>
Reply-To: <sthomas@optionshouse.com>
Organization: Peak6
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Jeff Janes <jeff.janes@gmail.com>
CC: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Tablespace-derived stats?
References: <508163B5.6070902@optionshouse.com>
	<CAMkU=1zz5_rRfWokMjTCsxGR1Q-W=5ZAK+_Vj=mryXBnRD7RQw@mail.gmail.com>
In-Reply-To: 
 <CAMkU=1zz5_rRfWokMjTCsxGR1Q-W=5ZAK+_Vj=mryXBnRD7RQw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
content-transfer-encoding: 7bit
X-Originating-IP: [10.10.201.64]
X-Brightmail-Tracker: 
 H4sIAAAAAAAAA+NgFupmleLIzCtJLcpLzFFi42LhSuGV0O3LaQwwONVubDHt+yEmi+szzzE7
	MHnsnHWX3ePCvmnsAUxRDYw2iXl5+SWJJakKKanFybZK/gUlmfl5xR75pcWpCi6Zxck5iZm5
	qUVKCpkptkrmSgoFOYnJqbmpeSW2SokFBal5KUp2XAoYwAaoLDNPITUvOT8lMy/dVskz2F/X
	wsLUUtdQyS4eGSR0smTcu/qeqeAKS8XdXRuYGhifMncxcnBICJhI3Pwr3MXICWSKSVy4t54N
	JMwroC9xsJkXJMwioCox4d08JhCbTUBXYlL/CjYQW0hARaLv7A2wOL+AsMS+D03MILaoQJjE
	8p2bweK8AoISJ2c+YQGxRYDmXLrdAGYzC3hKdJxaxQhiCwsYSBz59ZIVYmaJxPP9R8DmcwoE
	SiycMocNot5W4sKc61C98hLb385hhqhXlVjRPJEN4nwFif9X3jFNYBSahWT1LCTts5C0L2Bk
	XsUoXlyWmJyRaVpQnFtSYKhXkJqYbaaXl1qyiREctafldjBOX6p4iFGAg1GJhzfgXkOAEGti
	WXFl7iFGCQ5mJRFeN/bGACHelMTKqtSi/Pii0pzU4kOMycAwm8gsJZqcD0woeSXxhsaGlqaW
	JmaW5sbGBqQJK4nz2vYpBQgJpAOTTnZqakFqEcwWJg5OqQbGzie8qy02JkRWCVyaWtQ0Z5vQ
	hIWyc1faLzu/9pSx7vL0yHrTZEXVKdanVmQfdTK7GK/qJinx6dL/TSohO78xHN/KKf7do2aT
	yXu2XzF9f2blLjr81KrZfN+5T1NcmRhFz/w9c2fDypajnt5Pluf0bvhS5PYp585nrjSxK36/
	qlVmav45eFXNRImlOCPRUIu5qDgRADdlDhQeAwAA
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201210/272
X-Sequence-Number: 48231

On 10/19/2012 10:05 AM, Jeff Janes wrote:

> http://www.postgresql.org/docs/9.0/static/sql-altertablespace.html

Yep. I realized my error was not checking the ALTER page after going 
through CREATE. I swore I remembered seeing it in the past, but was 
surprised it wasn't there.

I keep forgetting Postgres prefers a CREATE + ALTER style than 
overloading every CREATE with all ALTER options. Though in my opinion 
that just adds extra unnecessary steps.

-- 
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas@optionshouse.com

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email