| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Mike Mascari <mascarim(at)yahoo(dot)com> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] TRUNCATE TABLE patch |
| Date: | 1999-09-28 04:24:27 |
| Message-ID: | 199909280424.AAA00465@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Applied. Sorry for the delay. I think Tom Lane fixed the function
calls.
> I submitted a patch to the patches list several
> months ago which implemented Oracle's TRUNCATE TABLE
> statement in PostgreSQL and was wondering whether or
> not the patch was going to make it into current. I had
> the patch ready before the 6.5 release but 6.5 was
> already in beta at the time, so I waited until the
> 6.5 tree was split.
>
> Recent discussions with regard to the functioning of
> DROP TAPLE in transactions and changing heap_openr()
> to require a locking type affect the nature of the
> patch. TRUNCATE TABLE behaves like Oracle's DDL
> statements by committing the running transaction and
> starting a new one for the TRUNCATE operation
> (which generates no rollback information), or, as
> Bruce Momjian puts it "cheating".
>
> Any news?
>
> Just curious,
>
> Mike Mascari
> (mascarim(at)yahoo(dot)com)
>
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Bid and sell for free at http://auctions.yahoo.com
>
> ************
>
>
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 1999-09-28 04:26:21 | RE: [HACKERS] Vacuum analyze bug CAUGHT |
| Previous Message | Bruce Momjian | 1999-09-28 04:22:16 | Re: [HACKERS] Status report: long-query-string changes |