Robert Haas <robertmh...@gmail.com> writes:
> On Mon, Aug 9, 2010 at 4:18 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
>> Particular implementations might cope with such cases in useful ways, or
>> then again they might not.
> That doesn't seem like a big problem to me. I was assuming we'd need
> to remap when the size changed.
Well, as long as you can do that, sure. I'm concerned about what
happens if/when remapping fails (not at all unlikely in 32-bit address
spaces in particular). You mentioned that that would probably have to
be a PANIC condition, which I think I agree with; and that idea pretty
much kills any argument that this would be a good way to improve server
uptime.
Another issue is that if you're doing dynamic remapping you almost
certainly can't assume that the segment will appear at the same
addresses in every backend. We could live with that for shared buffers
without too much pain, but not so much for most other shared
datastructures.
> Also, I was assuming that we were
> going to use shms, not files.
It looked to me like the spec for mmap was the same either way.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
