Skip site navigation (1) Skip section navigation (2)

Re: Cygwin PostgreSQL Regression Test Problems (Revisited)

From: Jason Tishler <Jason(dot)Tishler(at)dothill(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-ports(at)postgresql(dot)org
Subject: Re: Cygwin PostgreSQL Regression Test Problems (Revisited)
Date: 2001-03-29 17:10:26
Message-ID: 20010329121026.B209@dothill.com (view raw or flat)
Thread:
Lists: pgsql-ports
Tom,

On Thu, Mar 29, 2001 at 11:40:08AM -0500, Tom Lane wrote:
> BTW, I note that we are trying to use Unix sockets here.  Does the bug
> still appear if you force pg_regress to use TCP connections?

I'm not sure if you already know this, but Cygwin Unix sockets are
actually implemented as TCP/IP sockets.  Anyway, I forced TCP connections
and got the same psql hang:

(gdb) p *conn
$1 = {pghost = 0xa016618 "localhost", pghostaddr = 0x0, 
  pgport = 0xa016628 "65432", pgunixsocket = 0x0, pgtty = 0xa016638 "", 
  pgoptions = 0xa016648 "", dbName = 0xa017188 "regression", 
  pguser = 0xa017168 "jt", pgpass = 0xa017178 "", Pfdebug = 0x0, 
  noticeHook = 0x67984e8c <defaultNoticeProcessor>, noticeArg = 0x0, 
  status = CONNECTION_STARTED, asyncStatus = PGASYNC_IDLE, 
  notifyList = 0xa0103e8, sock = 3, laddr = {sa = {sa_family = 0, 
      sa_data = '\000' <repeats 13 times>}, in = {sin_family = 0, 
      sin_port = 0, sin_addr = {s_addr = 0}, 
      __pad = "\000\000\000\000\000\000\000"}, un = {sun_family = 0, 
      sun_path = '\000' <repeats 107 times>}}, raddr = {sa = {sa_family = 2, 
      sa_data = "ÿ\230\177\000\000\001\000\000\000\000\000\000\000"}, in = {
      sin_family = 2, sin_port = 39167, sin_addr = {s_addr = 16777343}, 
      __pad = "\000\000\000\000\000\000\000"}, un = {sun_family = 2, 
      sun_path = "ÿ\230\177\000\000\001", '\000' <repeats 101 times>}}, 
  raddr_len = 16, be_pid = 0, be_key = 0, salt = "\000", lobjfuncs = 0x0, 
  inBuffer = 0xa0103f8 "", inBufSize = 16384, inStart = 0, inCursor = 0, 
  inEnd = 0, nonblocking = 0, outBuffer = 0xa014400 "", outBufSize = 8192, 
  outCount = 0, result = 0x0, curTuple = 0x0, 
  setenv_state = SETENV_STATE_IDLE, next_eo = 0x0, errorMessage = {
    data = 0xa016408 "", len = 0, maxlen = 256}, workBuffer = {
    data = 0xa016510 "", len = 0, maxlen = 256}, client_encoding = 0}

> But, evidently, it never is coming ready for write.

Any ideas on how to demonstrate this to the Cygwin community without
all of the PostgreSQL baggage.  Sorry, but I'm not very experienced
with sockets.

Thanks,
Jason

-- 
Jason Tishler
Director, Software Engineering       Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp.               Fax:   +1 (732) 264-8798
82 Bethany Road, Suite 7             Email: Jason(dot)Tishler(at)dothill(dot)com
Hazlet, NJ 07730 USA                 WWW:   http://www.dothill.com

In response to

pgsql-ports by date

Next:From: Alfred PerlsteinDate: 2001-03-29 19:57:30
Subject: Re: [ADMIN] Re: Re: [PORTS] pgmonitor and Solaris
Previous:From: Bruce MomjianDate: 2001-03-29 17:02:32
Subject: Re: Re: [PORTS] pgmonitor and Solaris

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group