From: Bruce Momjian <maillist@candle.pha.pa.us>
Message-Id: <199808061534.LAA04821@candle.pha.pa.us>
Subject: Re: [HACKERS] Large objects names
In-Reply-To: <Pine.LNX.3.96.980806065832.793I-100000@maidast.retep.org.uk>
	from Peter T Mount at "Aug 6, 1998  6:59:49 am"
To: peter@retep.org.uk (Peter T Mount)
Date: Thu, 6 Aug 1998 11:34:09 -0400 (EDT)
Cc: hackers@postgreSQL.org,
	pgsql-interfaces@postgreSQL.org (PostgreSQL-interfaces)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> On Wed, 5 Aug 1998, Bruce Momjian wrote:
> 
> > Currently, large objects are stored internally as xinv### and xinx###.
> > 
> > I would like to rename this for 6.4 to be _lobject_### to prevent
> > namespace collisions, and make them clearer for administrators.
> > 
> > However, this may cause problems for backward compatability for large
> > object users.  As I see there are going to be other new large object
> > things in 6.4, it may not be an issue.
> > 
> > Is is OK to rename them internally?
> 
> Shouldn't be a problem. JDBC does refer to the xin prefix with the
> getTables method, so it's simply a single change there.

So does ODBC.  Let's start using relkind = 'l', then I can change the
name in a later release, and no one will see the change.

-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)