| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Duplicate-rows bug reports |
| Date: | 2001-12-11 16:17:11 |
| Message-ID: | 17486.1008087431@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
If the recent problem reports from Kenoyer and Eustace are the same
thing you saw, then the problem must exist in 7.1 as well as current
sources.
The best idea I've had so far is that there's something going wrong in
old-style VACUUM, probably in the chain-moving code which is horridly
complex and has had several bugs found before. (Eustace's
heavily-updated single-row table would present a very long chain, so
that seems to fit.) But this does not explain your problem seen with
7.2 sources, unless you were using VACUUM FULL. Were you?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2001-12-11 16:19:36 | Re: Restoring large tables with COPY |
| Previous Message | Lee Kindness | 2001-12-11 16:05:34 | Bulkloading using COPY - ignore duplicates? |