libpgport vs libpgcommon - Mailing list pgsql-hackers

From Peter Eisentraut
Subject libpgport vs libpgcommon
Date
Msg-id 1381974080.19926.5.camel@vanquo.pezone.net
Whole thread Raw
Responses Re: libpgport vs libpgcommon  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
I wonder whether it was ever consciously decided what the dependency
relationship between libpgport and libpgcommon would be.  When I added
asprintf(), I had intuitively figured that libpgport would be the lower
layer, and so psprintf() in libpgcommon depends on vasprintf() in
libpgport.  I still think that is sound.  But working through the
buildfarm issues now it turns out that wait_result_to_str() in libpgport
depends on pstrdup() in libpgcommon.  That doesn't seem ideal.  I think
in this case we could move wait_error.c to libpgcommon.  But I would
like to know what the consensus on the overall setup is.




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH] pg_sleep(interval)
Next
From: Peter Eisentraut
Date:
Subject: Re: LDAP: bugfix and deprecated OpenLDAP API