Re: pg_dump ORDER BY

From: Nabil Sayegh <nsmail(at)sayegh(dot)de>
To: Joel Burton <jburton(at)scw(dot)org>
Cc: "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: pg_dump ORDER BY
Date: 2000-12-08 01:08:08
Message-ID: 3A303478.9162BFC1@sayegh.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Joel Burton wrote:

> SELECT * INTO foo_temp FROM foo ORDER BY primarykeycolumn;
>
> TRUNCATE foo;
>
> INSERT INTO foo SELECT * FROM foo_temp;
>
> This preserves triggers, ref.int., etc., and will put things physically
> in the right order. (The TRUNCATE won't call any delete triggers you
> have, but the INSERT will, so if you log/handle inserts in a special
> way, this might fill up your log/take some time.) )

That sounds interesting, but as i only need the dump sorted (not the
real data,
the order will be destroyed the next time we update) it would be enough
to
do the SELECT INTO.

cu
--
Nabil Sayegh

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Joel Burton 2000-12-08 01:37:56 Re: Uninstall Everything.
Previous Message Aarmel 2000-12-08 00:34:52 Grant all