At 7:47 PM +0100 3/10/07, Martijn van Oosterhout wrote:
On Sat, Mar 10, 2007 at 08:30:20AM -0500, Dan Sugalski wrote:
Possibly it won't. The machine the DB is on sees heavy access to
large files, to the point where parts of the database may get flushed
out of the OS buffer cache. I was workin
On Sat, Mar 10, 2007 at 08:30:20AM -0500, Dan Sugalski wrote:
> Possibly it won't. The machine the DB is on sees heavy access to
> large files, to the point where parts of the database may get flushed
> out of the OS buffer cache. I was working on the (possibly deeply
> flawed assumption) that I
At 1:01 AM -0500 3/10/07, Tom Lane wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
I assume I'll have to do a 64 bit build to use more than a few gig of
shared buffers. If I do that, though, am I going to have to do a
database dump and reload,
Yes, most likely, because you'll have changed M
Dan Sugalski <[EMAIL PROTECTED]> writes:
> I assume I'll have to do a 64 bit build to use more than a few gig of
> shared buffers. If I do that, though, am I going to have to do a
> database dump and reload,
Yes, most likely, because you'll have changed MAXALIGN and therefore the
data alignment
I've got an install of Postgres 8.2.3 on a Sun box that's ticking
over nicely -- I'm pretty happy with it and how it's performing. It's
a 32 bit build, and the machine I'm running it on has a lot of extra
memory.
I assume I'll have to do a 64 bit build to use more than a few gig of
shared buf
