AW: [HACKERS] Re: [GENERAL] drop/rename table and transactions - Mailing list pgsql-hackers

From Zeugswetter Andreas SEV
Subject AW: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Date
Msg-id 219F68D65015D011A8E000006F8590C603FDC19C@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
Responses Re: AW: [HACKERS] Re: [GENERAL] drop/rename table and transactions
List pgsql-hackers
> I look at this and question the value of allowing such fancy 
> things vs.
> the ability to look at the directory and know exactly what table is
> which file.  Maybe we can use file names like 23423_mytable 
> where 24323
> is the table oid and mytable is the table name.  That way, we can know
> the table, and they are unique too to allow RENAME TABLE to work.
> 
> 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 ?

Andreas 


pgsql-hackers by date:

Previous
From: Vadim Mikheev
Date:
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Next
From: Hiroshi Inoue
Date:
Subject: Re: [HACKERS] Re: [GENERAL] drop/rename table and transactions