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

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

On Mon, 10 Jul 2000, Bruce Momjian wrote:

> > On Mon, 10 Jul 2000, Tom Lane wrote:
> >
> > > The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> > > > a few questions:
> > >
> > > > 1. back patchable to v7.0.x tree?
> > >
> > > Yes, if you think it's worth the trouble. We don't see that many
> > > trouble reports about it. (The reason I fixed it just now is that
> > > I was having too many occurrences of the misbehavior due to bugs in
> > > my memory management stuff ;-).)
> >
> > somehow Tim has hit this condition ... if we could get it backpatched to
> > the v7.0.x tree, then at least we could tell him to grab latest sources
> > from cvsup?
>
> 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'? I think
that is what I'm getting confused on. I don't imagine that this problem
is that the client is requesting OID 10,000,00 when the table only
contains 10 tuples ... where is the server getting the knowledge about a
block that is past the end of the relation?

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Vince Vielhaber 2000-07-10 20:22:15 [WEBMASTER] 'www/html related.html'
Previous Message Bruce Momjian 2000-07-10 18:55:17 Re: pgsql/src/backend/storage/smgr (md.c)