Re: [HACKERS] DROP TABLE inside a transaction block - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: [HACKERS] DROP TABLE inside a transaction block
Date
Msg-id Pine.BSF.4.21.0003080148180.591-100000@thelab.hub.org
Whole thread Raw
In response to Re: [HACKERS] DROP TABLE inside a transaction block  (Lamar Owen <lamar.owen@wgcr.org>)
List pgsql-hackers
On Tue, 7 Mar 2000, Lamar Owen wrote:

> Let the tables be named by OID, and only OID.  Then, for admins' convenience,
> put in a flat file that is updated periodically, similarly to pg_pwd being a
> flat text dump of pg_shadow.  Since there's going to have to be a system
> table mapping table names to OID's anyway, a flat dump of said system table
> should be similarly done as pg_pwd.  Call it pg_realnames or something.  Have
> it have two columns: OID, and pathname (relative to PGDATA) of table.

This I would be against ... I personally hate the whole pg_hba.conf,
pg_pwd, etc 'flatfiles' ...

But, could there not be some way of 'extracting extended data' from the
backend?  ie. some sort of \d command that would provide you with
tablename+path+disk size+??

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: [HACKERS] DROP TABLE inside a transaction block
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] xlog.c.patch for cygwin port.