| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Javier de la Torre <jatorre(at)gmail(dot)com> |
| Cc: | "Leif B(dot) Kristensen" <leif(at)solumslekt(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: psql is slow and it does not take much resources |
| Date: | 2006-05-04 20:31:02 |
| Message-ID: | 20060504203102.GC97354@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, May 03, 2006 at 04:43:15PM +0200, Javier de la Torre wrote:
> Yes,
>
> Thanks. I am doing this now...
>
> Is definetly faster, but I will also discover now if there is a limit
> in a transaction side... I am going to try to insert into one single
> transaction 60 million records in a table.
>
> In any case I still don't understand how why PostgreSQL was not taking
> resources before without the transaction. If it has to create a
> transaction per insert I understand it will have to do more things,
> but why is not taking all resources from the machine? I mean, why is
> it only taking 3% of them.
Because a server has more than just CPU as a resource. In this case you
were undoubtedly limited by the drives that pg_xlog is on.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian G. Pflug | 2006-05-04 20:32:49 | Re: Alternative for vacuuming queue-like tables |
| Previous Message | Jim C. Nasby | 2006-05-04 20:30:24 | Re: psql is slow and it does not take much resources |