From: | Vladimir Kokovic <vladimir(dot)kokovic(at)gmail(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: sysSettings::Flush() |
Date: | 2012-10-09 16:21:39 |
Message-ID: | CAHsHPqe4vZQv0MfD+YwYypZ+UdwjT3-vWekKjEcbkZibcbjZeA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)pgadmin(dot)org> wrote:
> Hi
>
> On Sat, Oct 6, 2012 at 6:57 AM, Vladimir Kokovic
> <vladimir(dot)kokovic(at)gmail(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2012-10-09 17:08:21 | Re: sysSettings::Flush() |
Previous Message | Dave Page | 2012-10-09 16:01:07 | pgAdmin III commit: Fix setting of comments on PPAS procedures. |