On Jan 18, 2012, at 1:09 PM, Rick Dicaire wrote:
> No, I know what the indexes are. The scenario is there's 3 tables in
> the db that get clustered. Wanted to know in what order those 3 tables
> are reclustered when CLUSTER is exec'd with no args.
Ah, I see now. Sorry for the noise.
--
Scott Ri
On Wed, Jan 18, 2012 at 2:17 PM, Scott Ribe wrote:
> On Jan 18, 2012, at 11:59 AM, Tom Lane wrote:
>
>> AFAIR there is no specified order. It probably just seqscans pg_class,
>> so whatever physical order those tuples happen to have today is it.
>
> I'm pretty sure he meant: "in the case when CLU
On Jan 18, 2012, at 11:59 AM, Tom Lane wrote:
> AFAIR there is no specified order. It probably just seqscans pg_class,
> so whatever physical order those tuples happen to have today is it.
I'm pretty sure he meant: "in the case when CLUSTER was issued in the past to
cluster the table on some in
Rick Dicaire writes:
> How do I determine in what order tables are clustered when CLUSTER is
> executed with no args?
AFAIR there is no specified order. It probably just seqscans pg_class,
so whatever physical order those tuples happen to have today is it.
regards, tom l
On Wed, Jan 18, 2012 at 10:08 AM, Kevin Grittner
wrote:
>> Also, I've been tasked with finding and listing all the tables
>> that get CLUSTER'd when CLUSTER with no args is executed,
>
> http://www.postgresql.org/docs/8.1/interactive/catalog-pg-index.html
select relname as table from pg_class joi
Rick Dicaire wrote:
> Hi folks...pgsql 8.1 (we're migrating to 9.1 later this year).
Good idea.
> When running CLUSTER with no args, on tables with multiple
> indexes, do I understand correctly that the tables' primary key is
> the default index used?
To quote the fine documentations at:
Hi folks...pgsql 8.1 (we're migrating to 9.1 later this year).
Two things:
When running CLUSTER with no args, on tables with multiple indexes, do
I understand correctly that the tables' primary key is the default
index used?
Also, I've been tasked with finding and listing all the tables that
get
