Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Vadim Mikheev <vadim@krs.ru>
From: Vadim Mikheev <vadim@krs.ru>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Mike Mascari <mascarm@mascari.com>, Lamar Owen <lamar.owen@wgcr.org>, Tom Lane <tgl@sss.pgh.pa.us>, Lincoln Yeoh <lylyeoh@mecomb.com>, pgsql-general@postgreSQL.org, PostgreSQL Developers List <hackers@postgreSQL.org>
Date: 1999-11-29T05:59:22Z
Lists: pgsql-hackers
Bruce Momjian wrote: > > > if PostgreSQL could successfully rollback DDL statements sanely (and thus > > diverge from ORACLE). I guess I don't expect that to happen successfully > > until > > something the equivalent of TABLESPACES is implemented and there is a > > disassociation between table names, index names and their filesystem > > counterparts and to be able to "undo" filesystem operations. That, it seems > > to > > me, will be a major undertaking and not going to happen any time soon... > > Ingres has table names that don't match on-disk file names, and it is a > pain to administer because you can't figure out what is going on at the > file system level. Table files have names like AAAHFGE. I have to say that I'm going to change on-disk database/table/index file names to _OID_! This is required by WAL because of inside of log records there will be just database/table/index oids, not names, and after crash recovery will not be able to read pg_class to get database/table/index name using oid ... Vadim