From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Preliminary patch for FRONTEND |
Date: | 2004-10-01 12:23:26 |
Message-ID: | 200410011223.i91CNQn21993@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > The following patch addresses this issue by making libpgport usable
> > unchanged by client applications, and makes a special server version for
> > the backend.
>
> This raises some alarm bells for me. Why does a "port support" library
> need to distinguish whether it is running in frontend or backend?
> Certainly the standard Unix library calls that it is purporting to
> replace do not care.
Already described --- ereport, memory allocation, and thread safety.
> Also, the patch does both more and less than I'd expect from your
> description. Why are there no changes at all to C code? And how can
> you just remove, eg, dirmod.c and exec.c from pg_resetxlog?
Basically libpgport now is compiled for the frontend so it just gets it
from the link line rather than build its own.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2004-10-01 13:35:08 | Int_aggregate/pgstattuple minor fix |
Previous Message | Bruce Momjian | 2004-10-01 12:22:20 | Re: Preliminary patch for FRONTEND |