| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New FSM patch |
| Date: | 2008-09-11 12:16:49 |
| Message-ID: | 48C90C31.6070405@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zdenek Kotala wrote:
> Does we need random_bool to spread workload? It seems to me a useless,
> because it also invokes one backend to use more pages instead of using
> one which is already in buffer cache.I think that it should generate a
> lot of extra i/o. Do not forget WAL full page write for firstime
> modified page.
random_bool() is gone in the latest version of the patch, in favor of a
"next pointer". You must be looking at an old version, and I must've
forgotten to update the link in the Wiki. That change was discussed in
the "New FSM allocation policy" thread.
Anyway, here's is the new version for your convenience, and I also added
a paragraph to the README, mentioning that the tree is degenerated from
the right.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| fsm-lazy-3.patch.gz | application/x-gzip | 43.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2008-09-11 12:20:30 | Re: [PATCH] Cleanup of GUC units code |
| Previous Message | Merlin Moncure | 2008-09-11 12:10:23 | Re: Transaction Snapshots and Hot Standby |