Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.8.8/8.7.5) with ESMTP id CAA06793; Thu, 6 Aug 1998 02:00:02 -0400 (EDT) Received: (from maillist@localhost) by candle.pha.pa.us (8.8.5/8.8.5) id BAA25883; Thu, 6 Aug 1998 01:27:53 -0400 (EDT) From: Bruce Momjian Message-Id: <199808060527.BAA25883@candle.pha.pa.us> Subject: Re: [HACKERS] Large objects names In-Reply-To: <199808060353.XAA16595@candle.pha.pa.us> from Bruce Momjian at "Aug 5, 1998 11:53:58 pm" To: maillist@candle.pha.pa.us (Bruce Momjian) Date: Thu, 6 Aug 1998 01:27:53 -0400 (EDT) Cc: hackers@postgreSQL.org (PostgreSQL-development), pgsql-interfaces@postgreSQL.org (PostgreSQL-interfaces) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > 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? I will probably keep the current names for a few releases. Once interfaces start using the relkind field to identify them, rather than the xinv* naming, I will be able to change the names to anything else and no external interface will care. -- 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)