That is variant for somebody who don't want flush() on every setting.
My preferred value is 0 (immediately).
Belgrade, Serbia, 9.October 2012
On 10/9/12, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Sat, Oct 6, 2012 at 6:57 AM, Vladimir Kokovic
> <vladimir(dot)kokovic(at)gmail(dot)com> wrote:
>> New method sysSettings::Flush()
>> With this patch every server setting goes immediately in persistent
>> At this moment it goes in persistent storage only when pgAdmin is
>> normally finished.
>> For other settings every third request will immediately put settings
>> in persistent storage.
> What's the rationale for that? It doesn't seem like it would be very
> expensive to write all settings immediately.
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
In response to
pgadmin-hackers by date
|Next:||From: Dave Page||Date: 2012-10-09 17:08:21|
|Subject: Re: sysSettings::Flush()|
|Previous:||From: Dave Page||Date: 2012-10-09 16:01:07|
|Subject: pgAdmin III commit: Fix setting of comments on PPAS procedures.|