Re: Workaround for custom aggregate which would need "internal" as statetype

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
Cc: Postgresql-General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Workaround for custom aggregate which would need "internal" as statetype
Date: 2006-04-10 23:29:32
Message-ID: 1723.1144711772@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Florian G. Pflug" <fgp(at)phlo(dot)org> writes:
> Using perl, and a perl-hash was even slower, so I wrote my to c-functions
> (actualy c++), which use a STL hash_set to filter out duplicates.

This makes me fairly nervous, because what's going to ensure that the
memory used by the hash_set is reclaimed? Particularly if the query
errors out partway through?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Florian G. Pflug 2006-04-10 23:49:27 Re: Workaround for custom aggregate which would need "internal"
Previous Message Tom Lane 2006-04-10 23:24:39 Re: How to find the latest (partial) WAL file