Quoting Andy Colson :
On 2/1/2011 9:08 AM, Dario Beraldi wrote:
Hello,
From the documentation of CLUSTER table
(http://www.postgresql.org/docs/8.4/static/sql-cluster.html) I
understand that clustering can be achieved by re-creating the table like
this:
CREATE TABLE newtable AS
SELECT * FROM t
On 2/1/2011 10:17 AM, Dario Beraldi wrote:
Quoting Andy Colson :
On 2/1/2011 9:08 AM, Dario Beraldi wrote:
Hello,
From the documentation of CLUSTER table
(http://www.postgresql.org/docs/8.4/static/sql-cluster.html) I
understand that clustering can be achieved by re-creating the table like
thi
On 2/1/2011 9:08 AM, Dario Beraldi wrote:
Hello,
From the documentation of CLUSTER table
(http://www.postgresql.org/docs/8.4/static/sql-cluster.html) I
understand that clustering can be achieved by re-creating the table like
this:
CREATE TABLE newtable AS
SELECT * FROM table ORDER BY columnlis
Hello,
From the documentation of CLUSTER table
(http://www.postgresql.org/docs/8.4/static/sql-cluster.html) I
understand that clustering can be achieved by re-creating the table
like this:
CREATE TABLE newtable AS
SELECT * FROM table ORDER BY columnlist;
My question is: If I upload w
"Kopljan Michael" <[EMAIL PROTECTED]> writes:
> Table is physically ordered by primary key. I try to cluster table with :
> CLUSTER cluster_idx_dok" ON "ITerp"."Dok" ;
> but Table is still physically ordered by primary key.
What's your evidence for saying so?
regards, tom
I'm have this table :
CREATE TABLE "ITerp"."Dok" (
"id_dok" INTEGER DEFAULT "AutoIncGet"('Dok'::text) NOT NULL,
"sifvrste" CHAR(3) NOT NULL,
"id_objekat1" INTEGER DEFAULT 0,
"id_objekat2" INTEGER DEFAULT 0,
"id_partner" INTEGER DEFAULT 0,
"broj" INTEGER NOT NULL,
"ext
I'm have this table :
CREATE TABLE "ITerp"."Dok" (
"id_dok" INTEGER DEFAULT "AutoIncGet"('Dok'::text) NOT NULL,
"sifvrste" CHAR(3) NOT NULL,
"id_objekat1" INTEGER DEFAULT 0,
"id_objekat2" INTEGER DEFAULT 0,
"id_partner" INTEGER DEFAULT 0,
"broj" INTEGER NOT NULL,
"ext
