| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Erik Rijkers <er(at)xs4all(dot)nl> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Create libpgcommon, and move pg_malloc et al to it |
| Date: | 2013-02-12 16:01:37 |
| Message-ID: | 20130212160137.GC5901@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Erik Rijkers wrote:
> 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.
Hmm? I don't think this patch requires an initdb at all. It doesn't
touch the database contents at all, does it?
Patches that force an initdb are flagged as such by bumping
CATALOG_VERSION_NO.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2013-02-12 16:13:29 | Re: pgsql: Create libpgcommon, and move pg_malloc et al to it |
| Previous Message | Erik Rijkers | 2013-02-12 15:52:32 | Re: pgsql: Create libpgcommon, and move pg_malloc et al to it |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-02-12 16:05:55 | Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
| Previous Message | Erik Rijkers | 2013-02-12 15:52:32 | Re: pgsql: Create libpgcommon, and move pg_malloc et al to it |