ahammond/pg_rollingwindow — comment on commit 8e135a347835763dc54f2fb8fe5a09894099c828
File: pg_rollingwindow_api.sql line 493
By ahammond:

/*= [local]:ahammond#*/ \d foo
Table "public.foo"
Column │ Type │
Modifiers
────────┼──────────────────────────┼──────────────────────────────────────────────────────────────────────────────────────
id │ integer │ not null default
nextval('foo_id_seq'::regclass)
name │ bigint │ not null
ts │ timestamp with time zone │ not null default now()
rnd │ bigint │ not null default floor((random() *
(9223372036854775807::bigint)::double precision))
Indexes:
"foo_pkey" PRIMARY KEY, btree (id)
"foo_name_ts_key" UNIQUE CONSTRAINT, btree (name, ts)
"foo_rnd" btree (rnd) WHERE rnd < 10000
Number of child tables: 26 (Use \d+ to list them.)

/*= [local]:ahammond#*/ ALTER TABLE foo CLUSTER ON foo_rnd ;
ERROR: cannot cluster on partial index "foo_rnd"

On Fri, Nov 4, 2011 at 12:54 PM, Christopher Browne <
reply@reply.github.com>wrote:

> We cannot? Or does it just behave mighty badly?
>
> I have no doubt but that you're right that it's a bad idea, but I'm
> curious as to How Bad.
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/ahammond/pg_rollingwindow/commit/8e135a347835763dc54f2fb8fe5a09894099c828#commitcomment-696444
>