libpgport vs libpgcommon

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: libpgport vs libpgcommon
Date: 2013-10-17 01:41:20
Message-ID: 1381974080.19926.5.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2013-10-17 02:01:30 Re: LDAP: bugfix and deprecated OpenLDAP API
Previous Message Robert Haas 2013-10-17 01:14:02 Re: [PATCH] pg_sleep(interval)