Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 4158B6324A1
	for <pgsql-sql-postgresql.org@mail.postgresql.org>;
	Sun, 24 Jan 2010 22:17:23 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia,
	port 10024) with ESMTP id 83453-06 for
	<pgsql-sql-postgresql.org@mail.postgresql.org>;
	Mon, 25 Jan 2010 02:17:04 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 7E489630EAD
	for <pgsql-sql@postgresql.org>; Sun, 24 Jan 2010 22:17:12 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o0P2H9O8026885;
	Sun, 24 Jan 2010 21:17:09 -0500 (EST)
To: Kyle Bateman <kyle@actarg.com>
cc: pgsql-sql@postgresql.org
Subject: Re: clock command regression in pltcl? 
In-reply-to: <4B5A7E04.8030905@actarg.com> 
References: <4B5A7E04.8030905@actarg.com>
Comments: In-reply-to Kyle Bateman <kyle@actarg.com>
	message dated "Fri, 22 Jan 2010 21:41:40 -0700"
Date: Sun, 24 Jan 2010 21:17:09 -0500
Message-ID: <26884.1264385829@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.461 tagged_above=-10 required=5 tests=AWL=0.138,
	BAYES_00=-2.599
X-Spam-Level: 
X-Archive-Number: 201001/45
X-Sequence-Number: 33581

Kyle Bateman <kyle@actarg.com> writes:
> Is this a regression or is there a reason the clock command is no longer 
> accessible?

And the answer is ... it's an underdocumented implementation change
in Tcl's "clock" command.  You can find the explanation and patch at
http://archives.postgresql.org/pgsql-committers/2010-01/msg00369.php
Or, if you just need a quick workaround, use pltclu.

			regards, tom lane