Re: Problem with dblink regression test

From: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Problem with dblink regression test
Date: 2005-06-22 16:47:05
Message-ID: 20050622164705.GA84822@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Tue, Jun 21, 2005 at 08:49:12PM -0700, Joe Conway wrote:
> I think most people would expect that if they don't specify a port, they
> would be talking to the same postmaster that they are running under on
> whatever port it is using, not some compiled in default. So your
> proposal makes perfect sense to me. Then the dblink regression test
> would not specify a port at all, correct?

Actually, the regression test currently doesn't specify a port. If it
did we wouldn't have found this problem.
--
Jim C. Nasby, Database Consultant decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2005-06-22 16:48:21 commit_delay, siblings
Previous Message Jim C. Nasby 2005-06-22 16:45:47 Re: Problem with dblink regression test

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-06-22 16:48:05 Re: plperl validator function
Previous Message Jim C. Nasby 2005-06-22 16:45:47 Re: Problem with dblink regression test