> >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 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
- [HACKERS] Re: [SQL] possible row locking bug in 7.0.3 &am... Tom Lane
- Re: [HACKERS] Re: [SQL] possible row locking bug in ... Philip Warner
- Re: [HACKERS] Re: [SQL] possible row locking bug in ... Tom Lane
- Re: [HACKERS] Re: [SQL] possible row locking bug... Hiroshi Inoue
- RE: [HACKERS] Re: [SQL] possible row locking bug in ... Mikheev, Vadim
- RE: [HACKERS] Re: [SQL] possible row locking bug... Philip Warner
- Re: [HACKERS] Re: [SQL] possible row locking bug in ... Hiroshi Inoue
- Re: [HACKERS] Re: [SQL] possible row locking bug... Philip Warner
- RE: [HACKERS] Re: [SQL] possible row locking bug in ... Philip Warner
- Re: [HACKERS] Re: [SQL] possible row locking bug in ... Tom Lane
- RE: [HACKERS] Re: [SQL] possible row locking bug in ... Mikheev, Vadim
- RE: [HACKERS] Re: [SQL] possible row locking bug in ... Mikheev, Vadim
- Re: [HACKERS] Re: [SQL] possible row locking bug... Hiroshi Inoue
- Re: [HACKERS] Re: [SQL] possible row locking bug in ... Forest Wilkinson
- RE: [HACKERS] Re: [SQL] possible row locking bug in ... Mikheev, Vadim