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

From Vladimir Kokovic
Subject Re: sysSettings::Flush()
Date
Msg-id CAHsHPqe4vZQv0MfD+YwYypZ+UdwjT3-vWekKjEcbkZibcbjZeA@mail.gmail.com
Whole thread Raw
In response to Re: sysSettings::Flush()  (Dave Page <dpage@pgadmin.org>)
Responses Re: sysSettings::Flush()  (Dave Page <dpage@pgadmin.org>)
List pgadmin-hackers
Hi,

That is variant for somebody who don't want flush() on every setting.
My preferred value is 0 (immediately).

Best regards
Vladimir Kokovic
Belgrade, Serbia, 9.October 2012

On 10/9/12, Dave Page <dpage@pgadmin.org> wrote:
> 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: Dave Page
Date:
Subject: pgAdmin III commit: Fix setting of comments on PPAS procedures.
Next
From: Dave Page
Date:
Subject: Re: sysSettings::Flush()