| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Philip Warner'" <pjw(at)rhyme(dot)com(dot)au>, "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-sql(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1 |
| Date: | 2001-03-30 03:14:39 |
| Message-ID: | 8F4C99C66D04D4118F580090272A7A234D335D@sectorbase1.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
> >Reported problem is caused by bug (only one tuple version must be
> >returned by SELECT) and this is way to fix it.
> >
>
> I assume this is not possible in 7.1?
Just looked in heapam.c - I can fix it in two hours.
The question is - should we do this now?
Comments?
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Knox | 2001-03-30 03:33:42 | Re: Re: Call for platforms |
| Previous Message | Bruce Momjian | 2001-03-30 03:12:45 | User administration tool |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2001-03-30 04:02:28 | RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1 |
| Previous Message | Philip Warner | 2001-03-30 02:49:11 | RE: [HACKERS] Re: possible row locking bug in 7.0.3 & 7.1 |