From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Linreg <linreg(at)gmx(dot)net> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: pgAgent: I want to make a port to C++ Only |
Date: | 2013-09-10 07:58:56 |
Message-ID: | CA+OCxozraCnqX9tDqMugSS4tF3Beb6WTXr=MSrZfg_=1mKAMyg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi
On Mon, Sep 9, 2013 at 2:37 PM, Linreg <linreg(at)gmx(dot)net> wrote:
> # Phase 1
>
> + stay on base structure (programm flow)
>
> + backward compatibilty (commandline parameter, sql-schema)
That's definitely required.
> + remove wxWidget dependencies
>
> + replace all wx classes with c++ classes (std::string, stringstream, thread
> etc)
Yes.
> + logfile has csv structure, that is needed in Phase 2
Why? Not sure what that has to do with porting to C++?
> (like 2013-12-01 12:13|DEBUG|bla bla ...)
>
> + remove mutex
Err, again, why? The mutex is there for a reason.
> + replace connectstring parsing
>
>
>
> # Phase 2
>
> + new impelenting of commandline parsing
>
> + move pgagent schema in separat database (better access rights...) this
> need a patch for pgadmin
That's very unlikely to be accepted - we intentionally use the
maintenance database for that, rather than forcing the user to use a
different one.
> + file_fdw configuration to show logfile-entrys over a sql view
OK, well that explains the CSV format above, but of course, this will
only work if the agent is known to be on the same host. At present, we
don't know that.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Linreg | 2013-09-10 09:45:52 | Re: pgAgent: I want to make a port to C++ Only |
Previous Message | Linreg | 2013-09-09 13:37:53 | Re: pgAgent: I want to make a port to C++ Only |