Re: WAL logging problem in 9.4.3?
| От | Andres Freund |
|---|---|
| Тема | Re: WAL logging problem in 9.4.3? |
| Дата | |
| Msg-id | 20150710104425.GC26521@alap3.anarazel.de обсуждение исходный текст |
| Ответ на | Re: WAL logging problem in 9.4.3? (Heikki Linnakangas <hlinnaka@iki.fi>) |
| Список | pgsql-hackers |
On 2015-07-10 13:38:50 +0300, Heikki Linnakangas wrote: > In the long-term, I'd like to refactor this whole thing so that we never > WAL-log any operations on a relation that's created in the same transaction > (when wal_level=minimal). Instead, at COMMIT, we'd fsync() the relation, or > if it's smaller than some threshold, WAL-log the contents of the whole file > at that point. That would move all that > more-difficult-than-it-seems-at-first-glance logic from COPY and indexam's > to a central location, and it would allow the same optimization for all > operations, not just COPY. But that probably isn't feasible to backpatch. I don't think that's really realistic until we have a buffer manager that lets you efficiently scan for all pages of a relation :(
В списке pgsql-hackers по дате отправления: