| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Vladimir Kokovic <vladimir(dot)kokovic(at)gmail(dot)com> |
| Cc: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: sysSettings::Flush() |
| Date: | 2012-10-09 10:40:07 |
| Message-ID: | CA+OCxox05ehO9mtt5DcsriBAxoBC8865FjtoczTZDR+ODvUbJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
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 15:59:39 | pgAdmin III commit: Fix setting of comments on PPAS procedures. |
| Previous Message | Ashesh Vashi | 2012-10-08 13:24:22 | Re: Crash in pgadmin3 (Recent Files for postgresql.conf) |