| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | mischa(at)ca(dot)sophos(dot)com, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Solaris shared_buffers anomaly? |
| Date: | 2006-06-13 22:34:01 |
| Message-ID: | 20060613223401.GA47540@winnie.fuhr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Jun 13, 2006 at 06:22:07PM -0400, Tom Lane wrote:
> Mischa Sandberg <mischa(at)ca(dot)sophos(dot)com> writes:
> > vmstat showed that it was swapping like crazy.
> > Dropped shared_buffers back down again.
> > Swapping stopped.
>
> Does Solaris have any call that allows locking a shmem segment in RAM?
The Solaris 9 shmctl manpage mentions this token:
SHM_LOCK
Lock the shared memory segment specified by shmid in
memory. This command can be executed only by a process
that has an effective user ID equal to super-user.
--
Michael Fuhr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-06-13 22:39:51 | Re: Confirmation of bad query plan generated by 7.4 |
| Previous Message | Tom Lane | 2006-06-13 22:22:07 | Re: Solaris shared_buffers anomaly? |