From: | Leonardo Francalanci <m_lists(at)yahoo(dot)it> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us, simon(at)2ndquadrant(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Unlogged tables, persistent kind |
Date: | 2011-04-25 07:36:35 |
Message-ID: | 991879.62936.qm@web29012.mail.ird.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The only data we can't rebuild it's the heap. So what about an option for UNlogged indexes on a LOGged table? It would always preserve data, and it would 'only' cost a rebuilding of the indexes in case of an unclean shutdown. I think it would give a boost in performance for all those cases where the IO (especially random IO) is caused by the indexes, and it doesn't look too complicated (but maybe I'm missing something).
I proposed the unlogged to logged patch (BTW has anyone given a look at it?) because we partition data based on a timestamp, and we can risk loosing the last N minutes of data, but after N minutes we want to know data will always be there, so we would like to set a partition table to 'logged'.
Leonardo
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2011-04-25 08:54:45 | Re: Unlogged tables, persistent kind |
Previous Message | Robert Haas | 2011-04-25 07:14:16 | Re: Unlogged tables, persistent kind |