X-Original-To: pgsql-sql-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 5B5789FA18C for ; Wed, 13 Sep 2006 18:20:03 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 91217-09 for ; Wed, 13 Sep 2006 18:19:58 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.logix-tt.com (mail.logix-tt.com [212.211.145.186]) by postgresql.org (Postfix) with ESMTP id 2584F9FA17D for ; Wed, 13 Sep 2006 18:19:58 -0300 (ADT) Received: from kingfisher.intern.logix-tt.com (p549D1F34.dip0.t-ipconnect.de [84.157.31.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logix-tt.com (Postfix) with ESMTP id 607F965978; Wed, 13 Sep 2006 23:22:12 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id 9AB771809DD31; Wed, 13 Sep 2006 23:19:56 +0200 (CEST) Message-ID: <450875FC.9040907@logix-tt.com> Date: Wed, 13 Sep 2006 23:19:56 +0200 From: Markus Schaber Organization: Logical Tracking and Tracing International AG, Switzerland User-Agent: Thunderbird 1.5.0.5 (X11/20060812) MIME-Version: 1.0 To: Tom Lane Cc: PostgreSQL SQL List Subject: Re: Aggregates with internal state type? References: <45086B40.3000200@logix-tt.com> <16722.1158181987@sss.pgh.pa.us> In-Reply-To: <16722.1158181987@sss.pgh.pa.us> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.172 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200609/92 X-Sequence-Number: 26303 Hi, Tom, Tom Lane wrote: > Markus Schaber writes: >> This lead me to the question whether it is possible to use "internal" as >> state type for an Aggregate whose functions are implemented in C. > > No, because the system has no idea what the representation of an > "internal" state value might be, and in particular how to copy it. > The same goes for other pseudotypes. Ah, I see. So there's no possibility to pass some void* kind of intermediate data, I have to craft at least a dummy PostgreSQL datatype for it. This also solves the question how such things would be cleaned up in case of an intermediate error. Thanks, Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org