Re: beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ] - Mailing list pgsql-hackers

From Ian Lance Taylor
Subject Re: beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]
Date
Msg-id siy9vzo0tj.fsf@daffy.airs.com
Whole thread Raw
In response to Re: beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]  (Frank Joerdens <frank@joerdens.de>)
Responses Re: beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]
List pgsql-hackers
Frank Joerdens <frank@joerdens.de> writes:

> I just typed
> 
> $ mount
> 
> and I get
> 
> /tmp on swap read/write/setuid on Mon Jan 22 16:39:32 2001
> 
> for the /tmp directory, which looks distinctly odd to me. What kind of
> device is swap (I know what swap is normally but I didn't know you could
> mount stuff there . . . )??

That is a tmpfs file system which uses swap space for /tmp storage.
Both swap usage and /tmp compete for the same partition on the disk.
If you have a lot of swapping programs, you don't get to put much in
/tmp.  If you have a lot of files in /tmp, you don't get to run many
programs.

As far as I can recall, this is a Sun specific thing.

It's a reasonable idea on a stable system.  It's a pretty crummy idea
on a development system, or one with unpredictable loads.  My
experience is that either something goes crazy and fills up /tmp and
then you can't run anything else and you have to reboot, or something
goes crazy and fills up swap and then you can't write any /tmp files
and daemon processes start to silently die and you have to reboot.

Ian


pgsql-hackers by date:

Previous
From: "Rod Taylor"
Date:
Subject: pg_dump issues
Next
From: Peter Eisentraut
Date:
Subject: Re: beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]