| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Forest Wilkinson'" <fspam(at)home(dot)com>, 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-05-19 00:28:48 |
| Message-ID: | 3705826352029646A3E91C53F7189E3201662D@sectorbase2.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
> I see postgres 7.1.1 is out now. Was the fix for this
> problem included in the new release?
I fear it will be in 7.2 only.
> On Thursday 29 March 2001 20:02, Philip Warner wrote:
> > At 19:14 29/03/01 -0800, Mikheev, Vadim wrote:
> > >> >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?
> >
> > It's a bug; how confident are you of the fix?
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-05-19 00:39:09 | Re: Plans for solving the VACUUM problem |
| Previous Message | Tom Lane | 2001-05-19 00:27:15 | Re: Plans for solving the VACUUM problem |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2001-05-19 11:59:49 | Re: Help! Record logging |
| Previous Message | Ловпаче Айдамир | 2001-05-18 23:30:04 | Why indexes are not used when scanning from functions? |