On 6/19/17 00:42, Ashutosh Sharma wrote:
>> If we don't find unconv, isn't it better to fall back to non-UTF8
>> version rather than saying command not found?
> Well, if any of the ICU package is installed on our system then we
> will certainly find uconv command. The only case where we can see such
> error is when user doesn't have any of the ICU packages installed on
> their system and are somehow trying to perform icu enabled build and
> in such case the build configuration has to fail which i think is the
> expected behaviour. Anyways, it is not uconv that decides whether we
> should fallback to non-UTF8 or not. It's the ICU version that decides
> whether to stick to UTF8 or fallback to nonUTF8 version. Thanks.
How do we know we're running the uconv command from the installation
that we will compile against?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
