| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Multiple table entries? |
| Date: | 2009-08-23 19:51:08 |
| Message-ID: | 3282.1251057068@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> On Sun, Aug 23, 2009 at 7:34 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Urgh. I bet that's where the problem is then. Some path is failing
>> to clear that bit, or maybe there's a race condition that allows it
>> to become set incorrectly (ie right after somebody else adds a tuple).
> Well it only gets set in vacuum when we have the vacuum cleanout lock
> so I can't see it getting set incorrectly unless there's a simple
> logic error in vacuum. I just scanned it and it looks right to me.
heap_update is broken. Details left as an exercise for the reader
(hint: Heikki has blatantly ignored the WAL-logging rules in transam/README)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Ross | 2009-08-23 20:05:05 | Re: Multiple table entries? |
| Previous Message | Greg Stark | 2009-08-23 18:42:31 | Re: Multiple table entries? |