Re: 8.4 TODO item: make src/port support libpq and ecpg directly - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: 8.4 TODO item: make src/port support libpq and ecpg directly
Date
Msg-id 200803250002.m2P02Bh10012@momjian.us
Whole thread Raw
In response to 8.4 TODO item: make src/port support libpq and ecpg directly  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Added to TODO:

* Create three versions of libpgport to simplify client code
 http://archives.postgresql.org/pgsql-hackers/2007-10/msg00154.php


---------------------------------------------------------------------------

Tom Lane wrote:
> This business with having libpq and ecpg pull in src/port modules
> manually is getting unmaintainable.  I wonder whether we could persuade
> src/port to generate three versions of libpgport.a --- backend,
> frontend, and frontend-shlib-ready --- and then just -l the appropriate
> one in libpq and ecpg.  This'd waste a few cycles building modules that
> would never be used, but on the other hand we'd buy some of that back
> by not building the same object files three or four times.
> 
>             regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
> 
>                 http://www.postgresql.org/about/donate

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: proposal casting from XML[] to int[], numeric[], text[]
Next
From: Bruce Momjian
Date:
Subject: Re: Deprecating heap_formtuple/heap_modifytuple/heap_deformtuple