| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: could not truncate directory "pg_serial": apparent wraparound |
| Date: | 2011-06-09 15:09:23 |
| Message-ID: | 4DF09BD3020000250003E459@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from Heikki Linnakangas's message of jue jun 09 04:56:41
-0400 2011:
>
>> Fortunately the fix is very simple, we just need to set the
>> page_dirty flag whenever we modify an slru page. But clearly this
>> slru stuff needs more testing. It's pretty hard to write good
>> repeatable test cases for these things, though.
>
> Maybe reduce the number of SLRU buffers used?
That's a thought. I'll see about getting a build with
TEST_OLDSERXID defined and just one or two SLRU buffers for this,
and see if anything pops out of that.
.... after I finish reviewing Dan's patch from last night.
Thanks,
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-06-09 15:13:44 | Re: literature on write-ahead logging |
| Previous Message | Robert Haas | 2011-06-09 15:09:14 | Re: release slippage |