| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: FSM, now without WAL-logging |
| Date: | 2008-09-24 20:29:45 |
| Message-ID: | 48DAA339.3070805@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> Zdenek Kotala wrote:
>>> What's about truncate FSM during WAL replay of main fork truncation record?
>
>> That would work, except that there's no WAL record for truncating the
>> main fork.
>
> Whaddya mean there's no WAL record for that? smgrtruncate produces one.
Ooh, I didn't realize that!
Hmm. The smgrtuncate WAL record is generated after the file is
truncated, so there's still a small window there, where we can be left
with a truncated main fork, but no smgrtruncate record for it, and thus
the page of the FSM representing the truncated blocks doesn't get zeroed
at replay.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-09-24 20:36:41 | Re: FSM, now without WAL-logging |
| Previous Message | Robert Haas | 2008-09-24 20:27:37 | Re: Proposal of SE-PostgreSQL patches (for CommitFest:Sep) |