| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Edmund Mergl <E(dot)Mergl(at)bawue(dot)de> |
| Cc: | PostgreSQL Hackers Mailinglist <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] strange behavior of UPDATE |
| Date: | 1999-05-21 21:00:57 |
| Message-ID: | 6518.927320457@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Edmund Mergl <E(dot)Mergl(at)bawue(dot)de> writes:
> When loading 100.000 rows into the table
> everything works ok. Selects and updates
> are reasonable fast. But when loading
> 1.000.000 rows the select statements still
> work, but a simple update statement
> shows this strange behavior.
Can you provide a script or something to reproduce this behavior?
There are a number of people using Postgres with large databases
and not reporting any such problem, so I think there has to be some
special triggering condition; it's not just a matter of things
breaking at a million rows. Before digging into it, I'd like to
eliminate variables like whether I have the right test case.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-05-21 21:14:33 | Re: [HACKERS] strange behavior of UPDATE |
| Previous Message | Edmund Mergl | 1999-05-21 20:34:15 | strange behavior of UPDATE |