| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Weird ecpg failures on buildfarm NetBSD members |
| Date: | 2007-07-09 14:52:15 |
| Message-ID: | 9809.1183992735@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Today's puzzler for the curious:
Last night the buildfarm reported two ECPG-Check failures
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=salamander&dt=2007-07-08%2017:30:00
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=canary&dt=2007-07-08%2017:30:01
which promptly went away again. Judging by the timestamps these must
have been induced by Joe's PQconnectionUsedPassword() patch and fixed by
my subsequent tweaking, but how the heck did that result in an ecpg
failure? I think that the cause must have had something to do with his
inclusion of postgres_fe.h into libpq-fe.h, which I took out on the
grounds that it was an unacceptable pollution of client code namespace.
But exactly why/how did that break ecpg, and why did the failure only
manifest on NetBSD machines?
I don't really have time to investigate this, but would like to know
what happened.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2007-07-09 15:54:51 | Warm standby stall -- what debug info would help? |
| Previous Message | Zdenek Kotala | 2007-07-09 14:05:43 | Re: script binaries renaming |