| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Subject: | Re: SLRU limits |
| Date: | 2011-06-09 14:03:57 |
| Message-ID: | 22749.1307628237@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> It's awfully late in the release cycle, but how about we add another
> digit to the filenames used by SLRU, to up the limit?
It's way too late for that kind of thing, unless you are saying that SSI
in and of itself is going to cause a release slip. (Which I'm getting
the uncomfortable feeling may be true anyway.) That is not a one-line
kind of fix --- it is likely to have a lot of unforeseen consequences.
And who builds with smaller-than-default BLCKSZ anyway?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-06-09 14:07:29 | Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS |
| Previous Message | Robert Haas | 2011-06-09 13:49:24 | Re: postgresql 9.0.4 source compilation issue on OSX |