Re: common fe/be library (was Re: [PATCH] binary heap implementation)

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: common fe/be library (was Re: [PATCH] binary heap implementation)
Date: 2013-01-14 15:16:31
Message-ID: CAHyXU0ycs+1aqae3hPNTJcjp_sDO4kKyuD+3T-jh_LWgGaNozw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 14, 2013 at 4:55 AM, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com> wrote:
> At 2012-11-15 12:08:12 -0500, robertmhaas(at)gmail(dot)com wrote:
>>
>> Still, maybe we could have a src/framework directory that uses the
>> same trick to produce a libpgframework that frontend code can use,
>> and a lib pgframework_srv that can be linked into the backend.
>> That's might not actually be that much work; we'd just need to
>> clone all the existing src/port logic.
>
> Does anyone have further comments about Robert's idea above? Or
> alternative suggestions about how to structure a library of routines
> that can be used in either the backend or in client code (like the
> binary heap implementation)?

A couple observations:
*) Not sure about the name: something like "libcommon"?

*) This is useful and potentially good for many things. For example,
maybe type manipulation code could be pushed into the common library
at some point.

merlin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-01-14 15:22:48 Re: pg_ctl idempotent option
Previous Message Simon Riggs 2013-01-14 14:23:31 Re: [PATCH] COPY .. COMPRESSED