Re: pgsql/src/backend/storage/smgr (md.c)

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql/src/backend/storage/smgr (md.c)
Date: 2000-07-10 22:39:44
Message-ID: Pine.BSF.4.21.0007101939040.3314-100000@thelab.hub.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Mon, 10 Jul 2000, Tom Lane wrote:

> The Hermit Hacker <scrappy(at)hub(dot)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?

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2000-07-10 22:49:49 Re: pgsql/src/backend/storage/smgr (md.c)
Previous Message Tom Lane 2000-07-10 22:11:10 Re: pgsql/src/backend/storage/smgr (md.c)