Re: sysSettings::Flush() - Mailing list pgadmin-hackers

From Dave Page
Subject Re: sysSettings::Flush()
Date
Msg-id CA+OCxox05ehO9mtt5DcsriBAxoBC8865FjtoczTZDR+ODvUbJg@mail.gmail.com
Whole thread Raw
In response to sysSettings::Flush()  (Vladimir Kokovic <vladimir.kokovic@gmail.com>)
Responses Re: sysSettings::Flush()  (Vladimir Kokovic <vladimir.kokovic@gmail.com>)
List pgadmin-hackers
Hi

On Sat, Oct 6, 2012 at 6:57 AM, Vladimir Kokovic
<vladimir.kokovic@gmail.com> wrote:
> Hi,,
>
> New method sysSettings::Flush()
>
> With this patch every server setting goes immediately in persistent storage.
> 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


pgadmin-hackers by date:

Previous
From: Ashesh Vashi
Date:
Subject: Re: Crash in pgadmin3 (Recent Files for postgresql.conf)
Next
From: Dave Page
Date:
Subject: pgAdmin III commit: Fix setting of comments on PPAS procedures.