| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Command Prompt, Inc(dot)" <pgsql-hackers(at)commandprompt(dot)com> |
| Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tuptoaster.c must *not* use SnapshotAny |
| Date: | 2002-01-16 17:10:52 |
| Message-ID: | 10016.1011201052@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Command Prompt, Inc." <pgsql-hackers(at)commandprompt(dot)com> writes:
> Josh Drake here: Although I know that development has pretty much ceased
> on the 7.1 series. This bug, is potentially very serious for those who
> have the problem.
Well, based on our experiments last night, recovery is pretty simple:
vacuum the affected table. So it doesn't qualify as a critical problem
in my eyes, although surely it's a "must fix" for 7.2.
> The last time this came up (that I can find) is in August of 2001, so the
> bug is not frequent that we are aware of. However, as it appears the fix
> is simple should we apply a 7.1.3.1 or 7.1.4 that fixes this issue?
I don't think anyone has the energy to put out a 7.1.4. We seem to have
enough trouble getting 7.2 out the door.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB SD | 2002-01-16 17:24:53 | Re: tuptoaster.c must *not* use SnapshotAny |
| Previous Message | Peter Eisentraut | 2002-01-16 16:41:39 | Re: Procedural language permissions and consequences |