Re: AW: [HACKERS] Re: [GENERAL] drop/rename table and transactions

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Zeugswetter Andreas SEV <ZeugswetterA(at)wien(dot)spardat(dot)at>
Cc: "'PostgreSQL Developers List'" <hackers(at)postgresql(dot)org>
Subject: Re: AW: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Date: 1999-12-01 17:49:38
Message-ID: 199912011749.MAA23293@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > This doesn't solve Vadim's problem. His additional work would be to
> > write a line to the log file for each table create/delete saying I
> > deleted this table with this oid, and when reading back the
> > log, he has
> > to record the oid_username combination and use that to
> > translate his log
> > oids into actual filenames.
>
> Why that ?
>
> 24323_* will point to the correct table segments inside the db directory.
> No need to actually know what * matches to, no ?

True. If we go with tablename_OID format, then vadim will have to scan
directory and pick up all his oids and map them to file names before
spinning through the log. Yes, it is a little more work, but worth it.

If you put the oid at the beginning, it is easier, but it is still an
issue because you have to issues a scandir command to find the matching
name for each oid. Actually, he can do that no matter where the oid is
stored in the name. That may be the way he has to handle it.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kristofer Munn 1999-12-01 21:24:23 NOTICE: AbortTransaction and not in in-progress
Previous Message Bruce Momjian 1999-12-01 17:43:50 Re: [ADMIN] When postgres will be faster?