Hi !
I need to insert 500.000 records on a table frequently. It´s a bulk
insertion from my applicatoin.
I am with a very poor performance. PostgreSQL insert very fast until the
tuple 200.000 and after it the insertion starts to be really slow.
I am seeing on the log and there is a lot of transact
In the last exciting episode, [EMAIL PROTECTED] (Grupos) wrote:
> Hi !
>
> I need to insert 500.000 records on a table frequently. It´s a bulk
> insertion from my applicatoin.
> I am with a very poor performance. PostgreSQL insert very fast until
> the tuple 200.000 and after it the insertion start
I do mass inserts daily into PG. I drop the all indexes except my primary key and then use the COPY FROM command. This usually takes less than 30 seconds. I spend more time waiting for indexes to recreate.Patrick HatcherMacys.Com [EMAIL PROTECTED] wrote: -To: [EMAIL PROTECTED]From: Christoph
Hi All,Thanks for the information on replication tools!!
Now, I have a question regarding locking tables and updating tables that have a relationship to the locked table.I opened up two pgsql windows logged in using same userid.Let's say I lock a table "customerdata" on one window.begin;lock tabl
On Fri, 2004-12-03 at 20:53 -0500, Mike Rylander wrote:
> On Fri, 03 Dec 2004 06:38:50 -0800, Joshua D. Drake
> <[EMAIL PROTECTED]> wrote:
> > That's true :) One of the reasons the compaq's are expensive
> > is they supposedly use a quad board, even for the dual machine.
> > Which means a different
On Sat, 4 Dec 2004, sarlav kumar wrote:
> Thanks for the information on replication tools!!
> Now, I have a question regarding locking tables and updating tables
> that have a relationship to the locked table.
>
> I opened up two pgsql windows logged in using same userid.
> Let's say I lock a tab
Rodrigo,
> I need to insert 500.000 records on a table frequently. It´s a bulk
> insertion from my applicatoin.
> I am with a very poor performance. PostgreSQL insert very fast until the
> tuple 200.000 and after it the insertion starts to be really slow.
> I am seeing on the log and there is a lo
We're working with a Postgres database that includes a fairly large table
(100M rows, increasing at around 2M per day).
In some cases we've seen some increased performance in tests by splitting
the table into several smaller tables. Both 'UNION ALL' views, and the
superclass/subclass scheme work
