Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id BD51F635871 for ; Tue, 9 Jun 2009 14:41:04 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 46787-07 for ; Tue, 9 Jun 2009 14:41:03 -0300 (ADT) Received: from cvs.postgresql.org (cvs.postgresql.org [217.196.146.206]) by mail.postgresql.org (Postfix) with ESMTP id 9F618635861 for ; Tue, 9 Jun 2009 14:41:03 -0300 (ADT) Received: by cvs.postgresql.org (Postfix, from userid 1007) id 8931275331E; Tue, 9 Jun 2009 17:41:02 +0000 (UTC) MIME-Version: 1.0 To: pgsql-committers@postgresql.org Subject: pgsql: Restore dblink_current_query() to being a C-language function, so X-Mailer: activitymail 1.24, http://search.cpan.org/dist/activitymail/ Content-Type: text/plain Message-Id: <20090609174102.8931275331E@cvs.postgresql.org> Date: Tue, 9 Jun 2009 17:41:02 +0000 (UTC) From: tgl@postgresql.org (Tom Lane) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200906/130 X-Sequence-Number: 37334 Log Message: ----------- Restore dblink_current_query() to being a C-language function, so as to not create an ABI break between 8.3 and 8.4. It is still just a wrapper around the built-in current_query() function, but at a different implementation level. Per my proposal. Note: this change doesn't break 8.4beta installations, since their SQL-language definition of the function still works fine. Modified Files: -------------- pgsql/contrib/dblink: dblink.c (r1.80 -> r1.81) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/dblink.c?r1=1.80&r2=1.81) dblink.h (r1.21 -> r1.22) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/dblink.h?r1=1.21&r2=1.22) dblink.sql.in (r1.17 -> r1.18) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/dblink.sql.in?r1=1.17&r2=1.18)