| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql/src/backend/storage/smgr (md.c) |
| Date: | 2000-07-10 14:15:53 |
| Message-ID: | 157.963238553@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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 ;-).)
> 2. worth building a v7.0.3 release for?
I doubt it.
> 3. unless it already does so, might it be an idea to generate a warning
> or some such in the logs, with the "cause of the request"?
It logs the bogus block number, which is all that md.c knows ...
>> Prevent creating a boatload of empty segments when md.c is asked to
>> access a ridiculously large block number within a relation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2000-07-10 14:21:57 | Re: pgsql/src/backend/storage/smgr (md.c) |
| Previous Message | The Hermit Hacker | 2000-07-10 11:32:38 | Re: pgsql/src/backend/storage/smgr (md.c) |