| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | "Hannu Krosing" <hannu(at)tm(dot)ee>, "Rahul_Iyer" <rahul_iyer(at)persistent(dot)co(dot)in> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Speeding up operations |
| Date: | 2003-08-14 16:47:25 |
| Message-ID: | 001b01c36283$be5d28c0$c202a8c0@hplaptop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
----- Original Message -----
From: "Hannu Krosing" <hannu(at)tm(dot)ee>
> If you are inserting into an empty table with primary key (or other
> constraints), you can run ANALYZE on that table in 1-2 minutes after you
> have started the INSERTs, so that constraint-checking logic will do the
> right thing (use inedex for pk).
This is one of the things that pg_autovaccum attempts to do. If you are
doing a lot of inserts into a table, it will perform periodic analyze
commands. The threshold for performing analyze is much lower than the
threshold for vacuum. Also, inserts don't effect the count towards the
vacuum threshold, only the analyze threshold.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2003-08-14 17:00:26 | getaddrinfo() issues on UnixWare. |
| Previous Message | Carlos Guzman Alvarez | 2003-08-14 15:46:05 | SSL Connection / Windows + Cygwin + PostgreSQL 7.4 Beta 1 question |