From: Aldor <an@mediaroot.de>
To: cbuschini@carax.com
Cc: pgsql-sql@postgresql.org
Subject: Re: [ADMIN] COPY TO / COPY FROM
Date: Fri, 23 Sep 2005 16:52:02 +0100
Message-ID: <433424A2.8030403@mediaroot.de> (raw)
In-Reply-To: <43340A4B.3090108@carax.com>
References: <4333EB91.7020909@carax.com>
<4333EED5.4090903@mediaroot.de>
<4333F22B.5030703@carax.com>
<4333F71D.7070604@mediaroot.de>
<43340A4B.3090108@carax.com>
> I kown I can use pg_dump to perform that "back up" but I wanted to
> test performences.
pg_dump does the same.. if you same custom it makes binary (WITH BINARY)
but with compression.
Performance?
1. TOP: inserte into select ....
2. TOP: copy / pg_restore with uncompressed binary
3. TOP: copy / pg_restore with uncompressed text
4. TOP: pg_restore with compressed binary (custom format in pg_dump)
5. TOP: normal inserts...
This is my experience.
> PATH = /home/postgres//carax_exec.out
Be aware to give postgres write/read access to this file/dir - i think
the double "//" is typee
Cédric Buschini wrote:
> Aldor wrote:
>
>> What is the name of the table you want to dump?
>>
>>
> I kown I can use pg_dump to perform that "back up" but I wanted to test
> performences.
>
> The table is carax_exec
>
>> What is the exact path you try to dump it to?
>>
>>
> PATH = /home/postgres//carax_exec.out
>
>> What version of PostgreSQL do you have?
>>
>>
> uhmm 8.0
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: an@mediaroot.de, cbuschini@carax.com
Subject: Re: [ADMIN] COPY TO / COPY FROM
In-Reply-To: <433424A2.8030403@mediaroot.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox