Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA02621; Mon, 4 Nov 91 09:21:14 -0800
Message-Id: <9111041721.AA02621@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: Re: Getting OID
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
In-Reply-To: Your message of "Mon, 04 Nov 91 08:46:28 PST."
             <9111041646.AA01913@postgres.Berkeley.EDU> 
Date: Mon, 04 Nov 91 09:20:23 PST

In message <9111041646.AA01913@postgres.Berkeley.EDU> you write:
> Dear Postgres Designers
>   I would to know if there is a way to get the OID of an instance in the same
> time of it creation

As of now there isn't.  If you follow the mailling list you will know that
the idea of returning the oid as part of the string returned by PQexec() is 
currently being tossed around.  I don't think this idea would be suited to 
giving the oid value for anything except append commands. Copy, replace and 
'retrieve into' commands can update a very large number of tuples and 
therefore cause extremely long return strings to be sent. The primary 
purpose of the return value on these queries is merely to inform the 
front-end that the command executed correctly.  Clearly, Sending large 
amounts of unused data over a network is not going to help you break any 
speed records ;-)

Jeff Meredith
mer@postgres.berkeley.edu