Re: palloc unification

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndQuadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: palloc unification
Date: 2013-02-06 16:17:30
Message-ID: 6574.1360167450@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On 6 February 2013 14:38, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>> Yeah, I am doing this right now and the "shared" name doesn't seem so
>> good. "libpgframework" sounds decent. So since libpgport comes from
>> src/port, are we okay with src/framework and src/include/framework?

> "common" ?

> src/backend/common
> src/include/common

To me the term "framework" carries a lot of baggage that doesn't fit
this usage. "common" seems better.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2013-02-06 16:20:15 Re: sql_drop Event Trigger
Previous Message Dimitri Fontaine 2013-02-06 16:15:43 Re: sql_drop Event Trigger