Re: pgsql: Create libpgcommon, and move pg_malloc et al to it

From: "Erik Rijkers" <er(at)xs4all(dot)nl>
To: "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Create libpgcommon, and move pg_malloc et al to it
Date: 2013-02-12 15:52:32
Message-ID: 4c13a79c7c91fa1c072424695edb4136.squirrel@webmail.xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, February 12, 2013 15:55, Alvaro Herrera wrote:
> Create libpgcommon, and move pg_malloc et al to it
>

If at all possible, it would be handy (for testers) if initdb-forcing commits are flagged as such.

(it's not a big deal but I often have large databases in a dev/test-setup that take a while to
re-create...)

Thanks,

Erik Rijkers

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2013-02-12 16:01:37 Re: pgsql: Create libpgcommon, and move pg_malloc et al to it
Previous Message Alvaro Herrera 2013-02-12 15:46:36 pgsql: Rename "string" pstrdup argument to "in"

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2013-02-12 16:01:37 Re: pgsql: Create libpgcommon, and move pg_malloc et al to it
Previous Message Tom Lane 2013-02-12 15:50:44 Re: [HACKERS] JPA + enum == Exception