Re: regresssion script hole

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: regresssion script hole
Date: 2006-06-19 12:08:46
Message-ID: 449693CE.9090302@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stefan Kaltenbrunner wrote:

>Andrew Dunstan wrote:
>
>
>>Why are we actually looking up anything? Just so we can bind to a
>>listening socket?
>>
>>Anyway, maybe the box needs a lookup line in its /etc/resolv.conf to
>>direct it to use files first, something like
>>
>> lookup file bind
>>
>>Stefan, can you look into that? It would be a bit ugly if it's calling
>>DNS (and failing) to resolve localhost.
>>
>>
>
>
>no - resolving localhost works fine (both using /etc/hosts and through
>the dns-resolver) - and I infact verified that when we initially started
>to investigate that issue a while ago :-)
>
>
>
>

Why are we looking up 'kaltenbrunner.cc' at all then? In any case, can
we just try with that resolver line?

The question isn't whether is succeeds, it's how long it takes to
succeed. When I increased the pg_regress timeout it actually went
through the whole regression test happily. I suspect we have 2 things
eating up the 60s timeout here: loading the timezone db and resolving
whatever it is we are trying to resolve.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kenneth Marshall 2006-06-19 12:57:21 Re: Rethinking stats communication mechanisms
Previous Message Simon Riggs 2006-06-19 11:29:15 Re: sync_file_range()