| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: dblink regression failure in HEAD |
| Date: | 2010-07-13 04:25:52 |
| Message-ID: | 19246.1278995152@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> What this looks like to me is that dblink.c doesn't contain the fix
>> that the new regression test is checking for.
>>
>> pangolin is pulling from the git mirror, which I still don't trust
>> further than I can throw it. How about you?
> There is something very odd about that machine. It started failing 5
> days ago. Then it stopped, then it started again.
A few experiments later: I can reproduce the failure shown on pangolin
exactly if I revert the latest changes in sql/dblink.sql and
expected/dblink.out, while keeping dblink.c up to date. So I guessed
wrong on which file was out of sync, but I say confidently that this
is a repository sync problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Itagaki Takahiro | 2010-07-13 05:18:00 | Re: log files and permissions |
| Previous Message | Andrew Dunstan | 2010-07-13 03:32:32 | Re: dblink regression failure in HEAD |