pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Slow Inserts Again
16+ messages / 9 participants
[nested] [flat]

* Slow Inserts Again
@ 1999-05-03 13:21 Frank Morton <fmorton@base2inc.com>
  1999-05-03 13:28 ` Re: [SQL] Slow Inserts Again Vadim Mikheev <vadim@krs.ru>
  1999-05-03 13:50 ` Re: [SQL] Slow Inserts Again Herouth Maoz <herouth@oumail.openu.ac.il>
  1999-05-03 14:19 ` Re: [SQL] Slow Inserts Again Chris Bitmead <chris.bitmead@bigfoot.com>
  0 siblings, 3 replies; 16+ messages in thread

From: Frank Morton @ 1999-05-03 13:21 UTC (permalink / raw)
  To: pgsql-sql@hub.org

We have been down this path, but I am at the point
that I think this problem is so big, it makes postgreSQL
unusable for me and could cause big problems for
many of us with large databases. Especially if you
need to reload your data, say, going to 6.5.

I have a database that has a dozen or so tables, but
one table in particular has about 60 fields that are all
character fields ranging in size from 16 bytes to 128.
This table has about 150,000 records. I have a text
file with insert statements, one per line, that I feed
through standard input to psql.

I have tried many combinations of things to speed this
up as you all have suggested. I have had no success
using "copy" at all because of problems with quotes
and other punctuation in the data.

This last attempt, I bracket each insert statement with
"begin;" and "end;".

What I am seeing this time around is in the beginning,
the inserts were reasonable in speed. Say 6 or 7
per second. But now that it is up to record 100,000 or
so (3 DAYS later) the time between inserts is about
10 SECONDS. As progress is made, the inserts
continue to get slower and slower. So at the current
rate, I have another 138 hours before completion!

This is on a fast Red Hat 5.2 machine. Plenty of RAM,
Ultra-wide scsi, 450 MHz Pentium II.

No index tables exist in the database while reloading.
I will build them after loading the data.

My biggest fear is as this database continues to grow,
headed toward 500,000 records or more, it seems that
it will reach the point (I may already have) that the data
can not ever be reloaded again, which is a scary
situation.

I'm still searching for help. Thanks.






^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
  1999-05-03 13:21 Slow Inserts Again Frank Morton <fmorton@base2inc.com>
@ 1999-05-03 13:28 ` Vadim Mikheev <vadim@krs.ru>
  2 siblings, 0 replies; 16+ messages in thread

From: Vadim Mikheev @ 1999-05-03 13:28 UTC (permalink / raw)
  To: Frank Morton <fmorton@base2inc.com>; +Cc: pgsql-sql@hub.org

Frank Morton wrote:
> 
> This last attempt, I bracket each insert statement with
                               ^^^^^^^^^^^^^^^^^^^^^
> "begin;" and "end;".

Why _each_?
Enclose ALL statements by begin; & end; to insert ALL data
in SINGLE transaction:

begin;
insert ....;
insert ....;
...
insert ....;
end;

Vadim



^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
  1999-05-03 13:21 Slow Inserts Again Frank Morton <fmorton@base2inc.com>
@ 1999-05-03 13:50 ` Herouth Maoz <herouth@oumail.openu.ac.il>
  2 siblings, 0 replies; 16+ messages in thread

From: Herouth Maoz @ 1999-05-03 13:50 UTC (permalink / raw)
  To: Frank Morton <fmorton@base2inc.com>; pgsql-sql@hub.org

At 16:21 +0300 on 03/05/1999, Frank Morton wrote:


> I have tried many combinations of things to speed this
> up as you all have suggested. I have had no success
> using "copy" at all because of problems with quotes
> and other punctuation in the data.

I must tell you, this doesn't sound reasonable to me. It's usually very
easy, if you already have a program that writes down the fields, to make
sure it scans the contents thereof and adds a backslash before each tab,
newline and backslash in every one of the fields.

If what you need is to dump-reload, then this is exactly what the dump
program will do for you.

> This last attempt, I bracket each insert statement with
> "begin;" and "end;".

Not necessary. An insert has an implicit begin-end around it. If you want
to change that behaviour, group several inserts together in begin-end.
Putting them individually is redundant.

> What I am seeing this time around is in the beginning,
> the inserts were reasonable in speed. Say 6 or 7
> per second. But now that it is up to record 100,000 or
> so (3 DAYS later) the time between inserts is about
> 10 SECONDS. As progress is made, the inserts
> continue to get slower and slower. So at the current
> rate, I have another 138 hours before completion!

Perhaps you need to break the connection. That is, every 1000 records,
disconnect from the backend, and connect again. A vacuum every so often may
also help somewhat.

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma





^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
  1999-05-03 13:21 Slow Inserts Again Frank Morton <fmorton@base2inc.com>
@ 1999-05-03 14:19 ` Chris Bitmead <chris.bitmead@bigfoot.com>
  2 siblings, 0 replies; 16+ messages in thread

From: Chris Bitmead @ 1999-05-03 14:19 UTC (permalink / raw)
  To: pgsql-sql@hub.org


Yes, it's normal in this situation to do a number in each transaction,
maybe a few thousand.

But the fact that copy doesn't work for you is a worry. Getting this
fixed seems like the best option.

Frank Morton wrote:
> 
> We have been down this path, but I am at the point
> that I think this problem is so big, it makes postgreSQL
> unusable for me and could cause big problems for
> many of us with large databases. Especially if you
> need to reload your data, say, going to 6.5.
> 
> I have a database that has a dozen or so tables, but
> one table in particular has about 60 fields that are all
> character fields ranging in size from 16 bytes to 128.
> This table has about 150,000 records. I have a text
> file with insert statements, one per line, that I feed
> through standard input to psql.
> 
> I have tried many combinations of things to speed this
> up as you all have suggested. I have had no success
> using "copy" at all because of problems with quotes
> and other punctuation in the data.
> 
> This last attempt, I bracket each insert statement with
> "begin;" and "end;".
> 
> What I am seeing this time around is in the beginning,
> the inserts were reasonable in speed. Say 6 or 7
> per second. But now that it is up to record 100,000 or
> so (3 DAYS later) the time between inserts is about
> 10 SECONDS. As progress is made, the inserts
> continue to get slower and slower. So at the current
> rate, I have another 138 hours before completion!
> 
> This is on a fast Red Hat 5.2 machine. Plenty of RAM,
> Ultra-wide scsi, 450 MHz Pentium II.
> 
> No index tables exist in the database while reloading.
> I will build them after loading the data.
> 
> My biggest fear is as this database continues to grow,
> headed toward 500,000 records or more, it seems that
> it will reach the point (I may already have) that the data
> can not ever be reloaded again, which is a scary
> situation.
> 
> I'm still searching for help. Thanks.

-- 
Chris Bitmead
http://www.bigfoot.com/~chris.bitmead
mailto:chris.bitmead@bigfoot.com



^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
@ 1999-05-03 13:50 Frank Morton <fmorton@base2inc.com>
  1999-05-03 13:52 ` Re: [SQL] Slow Inserts Again Jan Wieck <jwieck@debis.com>
  1999-05-03 14:06 ` Re: [SQL] Slow Inserts Again pierre@desertmoon.com
  1999-05-03 14:42 ` Re: [SQL] Slow Inserts Again Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 3 replies; 16+ messages in thread

From: Frank Morton @ 1999-05-03 13:50 UTC (permalink / raw)
  To: Vadim Mikheev <vadim@krs.ru>; +Cc: pgsql-sql@hub.org

>> This last attempt, I bracket each insert statement with
>                               ^^^^^^^^^^^^^^^^^^^^^
>> "begin;" and "end;".
>
>Why _each_?
>Enclose ALL statements by begin; & end; to insert ALL data
>in SINGLE transaction:

This was suggested by someone on the list so that all
150,000 inserts would not be treated as one large transaction.

Like I said before, I have tried all suggestions without success.







^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
  1999-05-03 13:50 Re: [SQL] Slow Inserts Again Frank Morton <fmorton@base2inc.com>
@ 1999-05-03 13:52 ` Jan Wieck <jwieck@debis.com>
  2 siblings, 0 replies; 16+ messages in thread

From: jwieck@debis.com @ 1999-05-03 13:52 UTC (permalink / raw)
  To: fmorton@base2inc.com; +Cc: vadim@krs.ru; pgsql-sql@hub.org

>
> >> This last attempt, I bracket each insert statement with
> >                               ^^^^^^^^^^^^^^^^^^^^^
> >> "begin;" and "end;".
> >
> >Why _each_?
> >Enclose ALL statements by begin; & end; to insert ALL data
> >in SINGLE transaction:
>
> This was suggested by someone on the list so that all
> 150,000 inserts would not be treated as one large transaction.
>
> Like I said before, I have tried all suggestions without success.

    For  huge  amounts  of  data I usually group the inserts into
    chunks of 1000 or so and enclose  the  chunks  by  BEGIN/END.
    Have you tried that already?


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#======================================== jwieck@debis.com (Jan Wieck) #





^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
  1999-05-03 13:50 Re: [SQL] Slow Inserts Again Frank Morton <fmorton@base2inc.com>
@ 1999-05-03 14:06 ` pierre@desertmoon.com
  2 siblings, 0 replies; 16+ messages in thread

From: pierre@desertmoon.com @ 1999-05-03 14:06 UTC (permalink / raw)
  To: fmorton@base2inc.com; +Cc: vadim@krs.ru; pgsql-sql@hub.org

Hmmm
  I've had problems with punctuation and stuff when importing large quantities
  of test into my DB. But I've always had success using copy. Have you tried
  using perl to munge your data and escape the appropriate characters?

  I've always used the following to import data into a clean DB.

  copy fubar from '/home/pierre/data/fubar.txt' using delimiters ',';

  How are you building your import files? That is how are you putting your data 
  together? 

  For me simply using a regex of: s/'/''/g  and s/,/\\,/g on each text field BEFORE I 
  dump it into my data file is sufficient to allow it to be imported using the copy
  command.

  So...for a table that has three varchar columns, A/B/C my data file might look
  like:

  However\, I''m here.,Don''t take me serisouly.,Hi there!

  The above would be imported correctly. I may be missing something as I just
  started reading this thread, but I hope this helps...

  -=pierre

> 
> >> This last attempt, I bracket each insert statement with
> >                               ^^^^^^^^^^^^^^^^^^^^^
> >> "begin;" and "end;".
> >
> >Why _each_?
> >Enclose ALL statements by begin; & end; to insert ALL data
> >in SINGLE transaction:
> 
> This was suggested by someone on the list so that all
> 150,000 inserts would not be treated as one large transaction.
> 
> Like I said before, I have tried all suggestions without success.
> 
> 
> 
> 
> 
> 




^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
  1999-05-03 13:50 Re: [SQL] Slow Inserts Again Frank Morton <fmorton@base2inc.com>
@ 1999-05-03 14:42 ` Tom Lane <tgl@sss.pgh.pa.us>
  1999-05-03 16:19   ` Re: [SQL] Slow Inserts Again Bruce Momjian <maillist@candle.pha.pa.us>
  1999-05-03 22:00   ` Re: [SQL] Slow Inserts Again Rudy Gireyev <rgireyev@cnmnetwork.com>
  2 siblings, 2 replies; 16+ messages in thread

From: Tom Lane @ 1999-05-03 14:42 UTC (permalink / raw)
  To: Frank Morton <fmorton@base2inc.com>; +Cc: Vadim Mikheev <vadim@krs.ru>; pgsql-sql@hub.org

>> Why _each_?
>> Enclose ALL statements by begin; & end; to insert ALL data
>> in SINGLE transaction:

But the transaction boundaries wouldn't have anything to do with
Frank's real problem, which is that the insertions are getting
slower and slower.  There's no good reason for that; and other
people are not reporting any comparable problems.  (Considering
that we *have* been getting trouble reports for more-than-2-gig
tables, it's clear that people are putting large amounts of data
into 6.5; so it's not like Frank is stressing the system more
than it has been before.)

Frank, what does the memory usage of the backend that's processing
this insertion look like; has it been growing steadily?  I'm wondering
whether you could have a problem with poor malloc behavior, or some
such.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
  1999-05-03 13:50 Re: [SQL] Slow Inserts Again Frank Morton <fmorton@base2inc.com>
  1999-05-03 14:42 ` Re: [SQL] Slow Inserts Again Tom Lane <tgl@sss.pgh.pa.us>
@ 1999-05-03 16:19   ` Bruce Momjian <maillist@candle.pha.pa.us>
  1 sibling, 0 replies; 16+ messages in thread

From: Bruce Momjian @ 1999-05-03 16:19 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Frank Morton <fmorton@base2inc.com>; Vadim Mikheev <vadim@krs.ru>; pgsql-sql@hub.org

> >> Why _each_?
> >> Enclose ALL statements by begin; & end; to insert ALL data
> >> in SINGLE transaction:
> 
> But the transaction boundaries wouldn't have anything to do with
> Frank's real problem, which is that the insertions are getting
> slower and slower.  There's no good reason for that; and other
> people are not reporting any comparable problems.  (Considering
> that we *have* been getting trouble reports for more-than-2-gig
> tables, it's clear that people are putting large amounts of data
> into 6.5; so it's not like Frank is stressing the system more
> than it has been before.)
> 
> Frank, what does the memory usage of the backend that's processing
> this insertion look like; has it been growing steadily?  I'm wondering
> whether you could have a problem with poor malloc behavior, or some
> such.

Yes, memory use it the place to look.  We have had bugs in the past that
did not free memory, causing this problem.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
  1999-05-03 13:50 Re: [SQL] Slow Inserts Again Frank Morton <fmorton@base2inc.com>
  1999-05-03 14:42 ` Re: [SQL] Slow Inserts Again Tom Lane <tgl@sss.pgh.pa.us>
@ 1999-05-03 22:00   ` Rudy Gireyev <rgireyev@cnmnetwork.com>
  1999-05-03 23:57     ` Re: [SQL] Slow Inserts Again Tom Lane <tgl@sss.pgh.pa.us>
  1 sibling, 1 reply; 16+ messages in thread

From: Rudy Gireyev @ 1999-05-03 22:00 UTC (permalink / raw)
  To: pgsql-sql@hub.org

Is it at all possible that the optimizer is responsible for this behaviour?
The reason I ask is that the fact that when the inserts start the optimizer is
working with a very small table, as the table grows larger the optimizer never
learns it because no VACUUM or VACUUM ANALYZE have been run.

If this is indeed the problem, then running VACUUM after every 10,000 inserts
would solve the problem.

Just curious what you folks think.

Rudy

On 3 May 99, at 12:19, Bruce Momjian wrote:

> > >> Why _each_?
> > >> Enclose ALL statements by begin; & end; to insert ALL data
> > >> in SINGLE transaction:
> > 
> > But the transaction boundaries wouldn't have anything to do with
> > Frank's real problem, which is that the insertions are getting
> > slower and slower.  There's no good reason for that; and other
> > people are not reporting any comparable problems.  (Considering
> > that we *have* been getting trouble reports for more-than-2-gig
> > tables, it's clear that people are putting large amounts of data
> > into 6.5; so it's not like Frank is stressing the system more
> > than it has been before.)
> > 
> > Frank, what does the memory usage of the backend that's processing
> > this insertion look like; has it been growing steadily?  I'm wondering
> > whether you could have a problem with poor malloc behavior, or some
> > such.
> 
> Yes, memory use it the place to look.  We have had bugs in the past that
> did not free memory, causing this problem.
> 
> -- 
>   Bruce Momjian                        |  http://www.op.net/~candle
>   maillist@candle.pha.pa.us            |  (610) 853-3000
>   +  If your life is a hard drive,     |  830 Blythe Avenue
>   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
> 
> 





^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
  1999-05-03 13:50 Re: [SQL] Slow Inserts Again Frank Morton <fmorton@base2inc.com>
  1999-05-03 14:42 ` Re: [SQL] Slow Inserts Again Tom Lane <tgl@sss.pgh.pa.us>
  1999-05-03 22:00   ` Re: [SQL] Slow Inserts Again Rudy Gireyev <rgireyev@cnmnetwork.com>
@ 1999-05-03 23:57     ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 16+ messages in thread

From: Tom Lane @ 1999-05-03 23:57 UTC (permalink / raw)
  To: rgireyev@cnmnetwork.com; +Cc: pgsql-sql@hub.org

"Rudy Gireyev" <rgireyev@cnmnetwork.com> writes:
> Is it at all possible that the optimizer is responsible for this behaviour?

Not in the sense that it might be choosing a bad plan --- there is only
one way to insert a tuple ;-).  Size of the table doesn't matter.

If the problem is indeed some kind of memory leak, the optimizer is as
likely a place for the leak as any other, I suppose.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
@ 1999-05-03 14:10 Frank Morton <fmorton@base2inc.com>
  1999-05-03 14:27 ` Re: [SQL] Slow Inserts Again Herouth Maoz <herouth@oumail.openu.ac.il>
  0 siblings, 1 reply; 16+ messages in thread

From: Frank Morton @ 1999-05-03 14:10 UTC (permalink / raw)
  To: pgsql-sql@hub.org; Herouth Maoz <herouth@oumail.openu.ac.il>

>> I have tried many combinations of things to speed this
>> up as you all have suggested. I have had no success
>> using "copy" at all because of problems with quotes
>> and other punctuation in the data.
>
>I must tell you, this doesn't sound reasonable to me. It's usually very
>easy, if you already have a program that writes down the fields, to make
>sure it scans the contents thereof and adds a backslash before each tab,
>newline and backslash in every one of the fields.

Is there a doc somewhere about what characters are treated
in some special way when doing a copy?







^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
  1999-05-03 14:10 Re: [SQL] Slow Inserts Again Frank Morton <fmorton@base2inc.com>
@ 1999-05-03 14:27 ` Herouth Maoz <herouth@oumail.openu.ac.il>
  0 siblings, 0 replies; 16+ messages in thread

From: Herouth Maoz @ 1999-05-03 14:27 UTC (permalink / raw)
  To: Frank Morton <fmorton@base2inc.com>; pgsql-sql@hub.org

At 17:10 +0300 on 03/05/1999, Frank Morton wrote:


> Is there a doc somewhere about what characters are treated
> in some special way when doing a copy?

Yes, the documentation of the COPY command. The essence is that if you use
the default delimiter (tab), you need to put a backslash before each tab,
newline and backslash in each of the text fields. Oh, and null fields
should be converted to \N.

It's all in the docs. Why don't you try to copy some of the rows into a
temporary table, and dump that table using pg_dump -a -t table_name dbname?
It may give you a clue.

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma





^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
@ 1999-05-03 15:33 Frank Morton <fmorton@base2inc.com>
  1999-05-03 15:47 ` Re: [SQL] Slow Inserts Again Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 16+ messages in thread

From: Frank Morton @ 1999-05-03 15:33 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Vadim Mikheev <vadim@krs.ru>; pgsql-sql@hub.org

>But the transaction boundaries wouldn't have anything to do with
>Frank's real problem, which is that the insertions are getting
>slower and slower.  There's no good reason for that; and other
>people are not reporting any comparable problems.  (Considering
>that we *have* been getting trouble reports for more-than-2-gig
>tables, it's clear that people are putting large amounts of data
>into 6.5; so it's not like Frank is stressing the system more
>than it has been before.)

I should have made it more clear. I am using 6.4.2 with the "limit"
addition.

>Frank, what does the memory usage of the backend that's processing
>this insertion look like; has it been growing steadily?  I'm wondering
>whether you could have a problem with poor malloc behavior, or some
>such.

Using "ps" there is only on process accumlating lots of time. One backend
process has accumulated 2036 minutes of cpu time. Using vmstat, it
looks like things are ok memory wise. Almost nothing swapped and
a few megabytes marked as free. The CPU is 0% idle. The whole system
is now starting to melt down, though. Even moving the mouse takes
a few seconds for it to move. But, looking around, I don't see any other
process doing anything really.

I'm up to 13 seconds now per insert.

I'm about to punt again and go back to figuring out how to make copy
work. At this point, I'd have to convert the insert statements to copy.

Thanks all for helping figure this out...

Frank







^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
  1999-05-03 15:33 Re: [SQL] Slow Inserts Again Frank Morton <fmorton@base2inc.com>
@ 1999-05-03 15:47 ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 16+ messages in thread

From: Tom Lane @ 1999-05-03 15:47 UTC (permalink / raw)
  To: Frank Morton <fmorton@base2inc.com>; +Cc: Vadim Mikheev <vadim@krs.ru>; pgsql-sql@hub.org

"Frank Morton" <fmorton@base2inc.com> writes:
> I'm about to punt again and go back to figuring out how to make copy
> work. At this point, I'd have to convert the insert statements to copy.

Well, it'd be worth your while to get the quoting conventions straight
so that you could use copy instead of inserts.  But since we don't know
where this slower-and-slower behavior is coming from, I worry that you
will still see it with a copy.  Copy will avoid a lot of SQL-parsing
and query-planning overhead, but it doesn't make any real difference
when it comes down to writing tuples on the disk, AFAIK.

If you stop the process now, and then start a new backend working on
the as-yet-uninserted data, is the new backend equally slow right away?
If it's a memory problem, a fresh backend might be OK for a while.
(This is the root of Herouth's suggestion to reconnect every few
thousand records...)

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 16+ messages in thread

* Re: [SQL] Slow Inserts Again
@ 1999-05-04 00:00 Frank Morton <fmorton@base2inc.com>
  0 siblings, 0 replies; 16+ messages in thread

From: Frank Morton @ 1999-05-04 00:00 UTC (permalink / raw)
  To: rgireyev@cnmnetwork.com; pgsql-sql@hub.org

>Is it at all possible that the optimizer is responsible for this behaviour?
>The reason I ask is that the fact that when the inserts start the optimizer
is
>working with a very small table, as the table grows larger the optimizer
never
>learns it because no VACUUM or VACUUM ANALYZE have been run.
>
>If this is indeed the problem, then running VACUUM after every 10,000
inserts
>would solve the problem.

Can I run a vacuum while inserts are still going?






^ permalink  raw  reply  [nested|flat] 16+ messages in thread


end of thread, other threads:[~1999-05-04 00:00 UTC | newest]

Thread overview: 16+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-05-03 13:21 Slow Inserts Again Frank Morton <fmorton@base2inc.com>
1999-05-03 13:28 ` Vadim Mikheev <vadim@krs.ru>
1999-05-03 13:50 ` Herouth Maoz <herouth@oumail.openu.ac.il>
1999-05-03 14:19 ` Chris Bitmead <chris.bitmead@bigfoot.com>
1999-05-03 13:50 Re: [SQL] Slow Inserts Again Frank Morton <fmorton@base2inc.com>
1999-05-03 13:52 ` Jan Wieck <jwieck@debis.com>
1999-05-03 14:06 ` pierre@desertmoon.com
1999-05-03 14:42 ` Tom Lane <tgl@sss.pgh.pa.us>
1999-05-03 16:19   ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-05-03 22:00   ` Rudy Gireyev <rgireyev@cnmnetwork.com>
1999-05-03 23:57     ` Tom Lane <tgl@sss.pgh.pa.us>
1999-05-03 14:10 Re: [SQL] Slow Inserts Again Frank Morton <fmorton@base2inc.com>
1999-05-03 14:27 ` Herouth Maoz <herouth@oumail.openu.ac.il>
1999-05-03 15:33 Re: [SQL] Slow Inserts Again Frank Morton <fmorton@base2inc.com>
1999-05-03 15:47 ` Tom Lane <tgl@sss.pgh.pa.us>
1999-05-04 00:00 Re: [SQL] Slow Inserts Again Frank Morton <fmorton@base2inc.com>

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