Re: PostgreSQL Write Performance - Mailing list pgsql-general

From Tim Uckun
Subject Re: PostgreSQL Write Performance
Date
Msg-id 855e4dcf1001051421t2e391c47kb9381657e0730057@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL Write Performance  ("Dann Corbit" <DCorbit@connx.com>)
Responses Re: PostgreSQL Write Performance  (Greg Smith <greg@2ndquadrant.com>)
Re: PostgreSQL Write Performance  (Craig Ringer <craig@postnewspapers.com.au>)
Re: PostgreSQL Write Performance  (Stephen Cook <sclists@gmail.com>)
Re: PostgreSQL Write Performance  (Dimitri Fontaine <dfontaine@hi-media.com>)
List pgsql-general
> You might use the copy command instead of insert, which is far faster.
> If you want the fastest possible inserts, then probably copy is the way
> to go instead of insert.
> Here is copy command via API:
> http://www.postgresql.org/docs/current/static/libpq-copy.html
> Here is copy command via SQL:
> http://www.postgresql.org/docs/8.4/static/sql-copy.html
>

Is there a command like COPY which will insert the data but skip all
triggers and optionally integrity checks.

pgsql-general by date:

Previous
From: Tim Uckun
Date:
Subject: Re: timestams in the the pg_standby output
Next
From: Greg Smith
Date:
Subject: Re: timestams in the the pg_standby output