| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: truncate vs. delete |
| Date: | 2008-07-24 14:33:12 |
| Message-ID: | dcc563d10807240733s4408372eoc676d05b393337c2@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
n Thu, Jul 24, 2008 at 7:53 AM, A. Kretschmer
<andreas(dot)kretschmer(at)schollglas(dot)com> wrote:
> am Thu, dem 24.07.2008, um 9:47:48 -0400 mailte Emi Lu folgendes:
>> I found a link for SQL Server, it applies to PostgreSQL 8.0.x as well?
>> http://vadivel.blogspot.com/2004/06/delete-vs-truncate-statement.html
>
> Not realy, for instance, pg can rollback a truncate, and a sequence are
> not reset.
Also you can truncate a table with foreign key references (using
cascade), something SQL Server apparently can't do either.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emi Lu | 2008-07-24 14:36:39 | Re: truncate vs. delete |
| Previous Message | A. Kretschmer | 2008-07-24 14:17:13 | Re: truncate vs. delete |