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 AAA26730 for ; Thu, 6 Aug 1998 00:00:03 -0400 (EDT) Received: (from maillist@localhost) by candle.pha.pa.us (8.8.5/8.8.5) id XAA16595 for hackers@postgreSQL.org; Wed, 5 Aug 1998 23:53:59 -0400 (EDT) From: Bruce Momjian Message-Id: <199808060353.XAA16595@candle.pha.pa.us> Subject: Large objects names To: hackers@postgreSQL.org (PostgreSQL-development) Date: Wed, 5 Aug 1998 23:53:58 -0400 (EDT) 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? -- 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)