Re: pgsql/src/backend/storage/smgr (md.c) - Mailing list pgsql-committers

From The Hermit Hacker
Subject Re: pgsql/src/backend/storage/smgr (md.c)
Date
Msg-id Pine.BSF.4.21.0007101939040.3314-100000@thelab.hub.org
Whole thread Raw
In response to Re: pgsql/src/backend/storage/smgr (md.c)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql/src/backend/storage/smgr (md.c)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On Mon, 10 Jul 2000, Tom Lane wrote:

> The Hermit Hacker <scrappy@hub.org> writes:
> >> Yes, but it is the cause of the problem that must be fixed.  This only
> >> prevents errors from creating too many segments.
>
> > Basically, if I'm understanding the problem from what Tom stated ... how
> > can the client side request 'a block past the end of the table'?
>
> It can't.  This patch just prevents md.c from going crazy as a
> consequence of a bug elsewhere in the backend that causes higher
> levels of the backend to request a garbage block number.
>
> The patch doesn't fix the underlying problem (ie, whatever higher-level
> bug might cause this); it just limits the extent of the bad
> consequences...

Okay, so I wasn't misunderstanding ... the bug is in *our* code, not in
the client code on Tim's side?


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql/src/backend/storage/smgr (md.c)
Next
From: Tom Lane
Date:
Subject: Re: pgsql/src/backend/storage/smgr (md.c)