| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | ZEUGSWETTER Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at> |
| Cc: | PostgreSQL Hackers Mailinglist <pgsql-hackers(at)postgreSQL(dot)org>, "'E(dot)Mergl(at)bawue(dot)de'" <E(dot)Mergl(at)bawue(dot)de> |
| Subject: | Re: [HACKERS] strange behavior of UPDATE |
| Date: | 1999-05-26 13:39:12 |
| Message-ID: | 12718.927725952@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
ZEUGSWETTER Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at> writes:
> can you run an: explain update bench set k500k = k500k + 1 where k100 = 30;
> I suspect it is doing a seq scan.
No, that's not it:
test=> explain update bench set k500k = k500k + 1 where k100 = 30;
NOTICE: QUERY PLAN:
Index Scan using k100 on bench (cost=179.05 rows=2082 width=154)
The benchmark loads the tables first and then builds indexes, and
in fact does a vacuum analyze after that! So the stats should be fine.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-05-26 13:42:30 | Re: [HACKERS] strange behavior of UPDATE |
| Previous Message | Horak Daniel | 1999-05-26 13:28:00 | report for Win32 port |