| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 13:29:16 |
| Message-ID: | 4C3C6A2C.2060309@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost wrote:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>
>> 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.
>>
>
> I'll check with Scott on this, sorry, but it might be an issue with the
> machine and not the repository. That's the box that he's been doing the
> performance-farm work on and it's entirely possible soemthing got
> screwed up there. Of course, it could also be a repository problem,
> I'll find out.
>
>
>
I just ran my validation script against the community git repo and it is
indeed broken in just this way :-(
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-07-13 14:10:03 | Re: explain.c: why trace PlanState and Plan trees separately? |
| Previous Message | Martin Pihlak | 2010-07-13 12:16:08 | Re: log files and permissions |