On Thu, 8 Apr 2004, Mikhail Ts wrote:
> I published message above to PostgreSQL list but didn't get any
> replies. Good news - I know what was causing problems - while debugging
> Courier I set up log_statement=true flag in PostgreSQL config file to
> see what exact queries get generated. If I change to default "false"
> Exim starts to work normally if I set to "true" - it goes the way I
> described earlier.
Extraordinary!
> By this time I've not only rebuilt all three
> programs several times but also upgraded my kernel to 2.4.25 version,
> made libpq statically linked into Exim, switched to Unix domain
> sockets, tried to attach to running Exim with gdb - still the same
> behaviour, except gdb message shown above. I'm very new to all this
You seem to have learned a lot about debugging and testing!
> and could be missing something obvious but it seemed to me that log
> setting shouldn't affect that much.
Indeed.
> I also wrote simple C program to access PostgreSQL and it shown that
> PostgreSQL returns back log record itself as a first row in query
> result(!) in this mode and that confuses hell out of pgsql lookup on
> Exim side.
I'm not surprised! That probably explains a lot of strange behaviour.
> Anyway - I got it running and like it very much, thank you.
I'm glad the problem has been resolved.
Philip
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
