-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 3/6/2012 8:32 AM, Robert Haas wrote: > On Mon, Mar 5, 2012 at 4:40 PM, Larry Rosenman <l...@lerctr.org> > wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> Is there any way to get more info out of CLUSTER VERBOSE so it >> says what index it's working on AFTER the table re-write? >> >> INFO: clustering "public.values" using sequential scan and sort >> INFO: "values": found 0 removable, 260953511 nonremovable row >> versions in 4224437 pages DETAIL: 0 dead row versions cannot be >> removed yet. CPU 168.02s/4324.68u sec elapsed 8379.12 sec. >> >> >> And at this point it's doing something(tm), I assume re-doing the >> indexes. >> >> It would be nice(tm) to get more info. >> >> Ideas? > > Try setting client_min_messages=DEBUG1. At least on current > sources that gives some additional, relevant output; I think that's > probably there in 9.1.x as well. > Thanks. That helps some, but I'd like to see: 1) these moved up to INFO when CLUSTER VERBOSE 2) time/statistics on each index build
INFO: clustering "public.values" using sequential scan and sort INFO: "values": found 0 removable, 260953511 nonremovable row versions in 4224437 pages DETAIL: 0 dead row versions cannot be removed yet. CPU 167.57s/4325.52u sec elapsed 7687.28 sec. DEBUG: building index "values_idx1" on table "values" DEBUG: building index "values_idx2" on table "values" DEBUG: building index "values_idx3" on table "values" DEBUG: building index "values_idx4" on table "values" DEBUG: building index "values_idx5" on table "values" DEBUG: building index "values_idx6" on table "values" DEBUG: building index "values_idx7" on table "values" DEBUG: building index "values_idx_cluster" on table "values" CLUSTER Time: 28997806.474 ms Comments? - -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPV3GyAAoJENC8dtAvA1zmAzkIALJL/Ir7Ks3gYVy4bVB7Oamc Etpg6/hmM3+g0Ry9Lv3yUbaeHLxwuAaW+Gv5nDuepZFbMfAxYjsUG+fVUu8n3Xo3 V42/4TFxI7QQUtnwqkkMo0Y1vBNsmIRFuxx3b2R+ePKAZaQFLoElU7dL1JOA1u3c OQ0dUDtiUNTSa+ZrNYNbLhqOUUIooGrF8hWLKfmLOrbrRpAObrCeyaHW2qxRrIq/ wbvHG7YG1byRiDzZr4DNKrS4/88HXjgo2m8xmxyNf+1fKsa69fkIA+rbsqyEx4ui RAih9fQVQcjcK15XTyDchT21YRdwDZnjVt/Yh0IMvDE19sIQFfrs1QTGPnUULpI= =5bZG -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
