RE: Proposal for DROP TABLE rollback mechanism

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: RE: Proposal for DROP TABLE rollback mechanism
Date: 2000-11-09 00:14:03
Message-ID: 8F4C99C66D04D4118F580090272A7A234D3164@sectorbase1.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Rollback of DROP TABLE now works in non-WAL code, and seems to work in
> WAL code too. I did not add WAL logging, because I'm not quite sure
> what to do, so rollforward probably does the wrong thing. Could you
> deal with that part? smgr.c is the place that keeps the list of what
> to delete at commit or abort.

Ok, thanks! I'll take list of relfilenodes to delete just before
commit and put it into commit record.

Vadim

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff MacDonald 2000-11-09 01:44:51 test .. ignore
Previous Message Luis Magaa 2000-11-08 23:47:44 Text concat problem