Re: danger of stats_temp_directory = /dev/shm - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: danger of stats_temp_directory = /dev/shm
Date
Msg-id 20130820044544.GA6564@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: danger of stats_temp_directory = /dev/shm  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> > Pushed with those fixes, thanks.  I noticed we also needed to match
> > files global.stat and global.tmp.  Also I added another conversion to
> > the sscanf pattern, to ignore files named "db_1234.tmp.foo" and such
> > (i.e.  stuff after whitespace).
> 
> After reading the sscanf man page, it seemed like this still wasn't
> covering all the bases about where sscanf will silently skip whitespace,
> so I hacked it a bit more.

Funnily enough, my own reading of that manpage got me a flawed
understanding of %n -- I interpreted it as returning the number of items
matched, not the number of chars read .. and I was precisely looking for
a way to determine the latter.  Thanks.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Next
From: Alvaro Herrera
Date:
Subject: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])