Bruce Momjian <[EMAIL PROTECTED]> writes:
> Yes, thread.c, path.c, and sprompt.c should be in utils, but how do I do
> that? Utils seems to be a place things are pulled from, rather than a
> library that goes with every link.
> Is it worth creating another library that acts just like /port but is
> called utils, or should we just rename the directory to portutils?
path.c is arguably okay material for /port, since it is dealing with
platform-to-platform variations.
sprompt.c is only going to be used by stuff under src/bin. I wonder if
we should create a src/bin/utils directory.
Not sure about thread.c --- perhaps we could just dump it into libpq.
(libpq requires it anyway, no? So why not export it from there and let
the apps atop libpq use the same instance.)
> I am looking to move fmtId() over to port too so psql can use it. It is
> already used by pg_dump, and /scripts.
That's definitely not port/ material. A src/bin/utils/ directory would
make sense for it though.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
