Re: patch: tsearch - some memory diet - Mailing list pgsql-hackers

From Robert Haas
Subject Re: patch: tsearch - some memory diet
Date
Msg-id AANLkTi=QjrWSf5=YqDm8EZEabo_FRtS86RmZQ=xYfYtc@mail.gmail.com
Whole thread Raw
In response to Re: patch: tsearch - some memory diet  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: patch: tsearch - some memory diet
Re: patch: tsearch - some memory diet
List pgsql-hackers
On Tue, Sep 7, 2010 at 1:30 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> In the particular case here, the dictionary structures could probably
> safely use such a context type, but I'm not sure it's worth bothering
> if the long-term plan is to implement a precompiler.  There would be
> no need for this after the precompiled representation is installed,
> because that'd just be one big hunk of memory anyway.

Rather than inventing something more complex, I'm inclined to say we
should just go ahead and apply this more or less as Pavel wrote it.  I
haven't tried to reproduce Pavel's results, but I assume that they are
accurate and that's a pretty big savings for a pretty trivial amount
of code.  If it gets thrown away later when/if someone codes up a
precompiler, no harm done.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Itagaki Takahiro
Date:
Subject: Re: Help with User-defined function in PostgreSQL with Visual C++
Next
From: Robert Haas
Date:
Subject: Re: Help with User-defined function in PostgreSQL with Visual C++