| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Felipe Santos *EXTERN*" <felipepts(at)gmail(dot)com> |
| Cc: | Alex Goncharov *EXTERN* <alex(dot)goncharov(dot)usa(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: autocommit (true/false) for more than 1 million records |
| Date: | 2014-08-27 12:41:50 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17D2F06F@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
[about loadling large amounts of data]
Felipe Santos wrote:
> This might also help:
> http://www.postgresql.org/docs/9.1/static/populate.html
>
>
> Bulk load tables from text files in almost all RDMS are "log free" (Postgres' COPY is one of them).
>
> The reason is that the database doesn't need to waste resources by writing the log because there's no
> risk of data loss. If the COPY operation fails, your data will still live in the text files you're
> trying to bulk load from.
That is only true if the table was created in the same transaction as the COPY statement.
Otherwise it could be that recovery starts after CREATE TABLE but before COPY, and
it would have to recover the loaded data.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2014-08-27 12:59:29 | Re: autocommit (true/false) for more than 1 million records |
| Previous Message | Felipe Santos | 2014-08-27 11:50:52 | Re: autocommit (true/false) for more than 1 million records |