| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
| 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:11:10 |
| Message-ID: | 4969.963267070@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:
>> 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...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2000-07-10 22:39:44 | Re: pgsql/src/backend/storage/smgr (md.c) |
| Previous Message | Vince Vielhaber | 2000-07-10 20:22:15 | [WEBMASTER] 'www/html related.html' |