Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.10.1/8.10.1) with ESMTP id e5GF53N58913
	for <pgsql-interfaces@postgresql.org>;
	Fri, 16 Jun 2000 11:05:04 -0400 (EDT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id LAA07252;
	Fri, 16 Jun 2000 11:04:58 -0400 (EDT)
To: Nissim <nissim@nksystems.com>
cc: pgsql-interfaces@postgresql.org
Subject: Re: [PATCH] Datatype of OID should be VARBINARY, not INT 
In-reply-to: <394A3D07.C1542D05@nksystems.com> 
References: <394A3D07.C1542D05@nksystems.com>
Comments: In-reply-to Nissim <nissim@nksystems.com>
	message dated "Fri, 16 Jun 2000 10:43:19 -0400"
Date: Fri, 16 Jun 2000 11:04:57 -0400
Message-ID: <7249.961167897@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200006/71

Nissim <nissim@nksystems.com> writes:
> The datatype returned by the ResultSetMetaData for OID should be
> VARBINARY, not INT.

Uh, why?  There's nothing VAR about it that I can see, and it is
the same size as INT ... at the moment anyway ...

			regards, tom lane