| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)mail(dot)hub(dot)org> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql/src/backend/storage/smgr (md.c) |
| Date: | 2000-07-10 11:32:38 |
| Message-ID: | Pine.BSF.4.21.0007100831200.3314-100000@thelab.hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
a few questions:
1. back patchable to v7.0.x tree?
2. worth building a v7.0.3 release for?
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"?
On Mon, 10 Jul 2000, Tom Lane wrote:
> Date: Monday, July 10, 2000 @ 00:32:00
> Author: tgl
>
> Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/storage/smgr
> from hub.org:/home/projects/pgsql/tmp/cvs-serv54321
>
> Modified Files:
> md.c
>
> ----------------------------- Log Message -----------------------------
>
> Prevent creating a boatload of empty segments when md.c is asked to
> access a ridiculously large block number within a relation.
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-07-10 14:15:53 | Re: pgsql/src/backend/storage/smgr (md.c) |
| Previous Message | Tom Lane | 2000-07-10 04:32:01 | pgsql/src/backend/storage/smgr (md.c) |