Re: pg_stat_*_columns?
От | Andres Freund |
---|---|
Тема | Re: pg_stat_*_columns? |
Дата | |
Msg-id | 20150621155336.GD9243@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: pg_stat_*_columns? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pg_stat_*_columns?
|
Список | pgsql-hackers |
On 2015-06-20 10:55:03 -0400, Tom Lane wrote: > I dunno that tweaking the format would accomplish much. Where I'd love > to get to is to not have to write the data to disk at all (except at > shutdown). But that seems to require an adjustable-size shared memory > block, and I'm not sure how to do that. One idea, if the DSM stuff > could be used, is to allow the stats collector to allocate multiple > DSM blocks as needed --- but how well would that work on 32-bit > machines? I'd be worried about running out of address space. We could also just mmap() the stats file into memory in various processes. With a bit care it should be quite possible to only mmap a subsets of the file at once, taking care of the address space issues. There'll be some interesting problems to solve for both DSM and mmap based solutions to make the locking work nicely. I guess most of it should be doable quite sensibly using atomics; but the emulation on older platforms might mean that we'd need to serialize at restarts.
В списке pgsql-hackers по дате отправления: