Skip site navigation (1) Skip section navigation (2)

Re: about truncate

From: "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec>
To: "David Fetter" <david(at)fetter(dot)org>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: about truncate
Date: 2008-12-30 21:07:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Tue, Dec 30, 2008 at 2:00 PM, David Fetter <david(at)fetter(dot)org> wrote:
> Here's one such use-case.  Let's say a table has gotten large and
> you've decided to partition it.  You add child tables, add one or more
> triggers to the parent table to make sure it never gets a row,
> populate the child tables from the parent table, then you want to
> remove all the rows from the parent table.

you're spying me? exactly that happen to me... ;)

my first attempt was to execute TRUNCATE ONLY... and gives me an error
and the thread begun...

Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to


pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2008-12-31 00:33:26
Subject: Re: incoherent view of serializable transactions
Previous:From: Tom LaneDate: 2008-12-30 20:49:51
Subject: WIP patch for basic window frame support

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group