Обсуждение: pgAdmin v1.10.0 Beta 1
Two things: 1) Has the mixed slashes on the certificate file been fixed? 2) With respect to the error: "Error connecting to server: root certificate file." This was not present in earlier versions of pgAdminIII, notably 8.3. is this a feature of the new program and if so are there instructions on how to fix this in windows/linux? I have only tried windows not linux. By the way this error is not present for a localhost connection. Overall it is very nice, the SQL Graphical Query builder looks intuitive and easy to use. Andrew -- ___________________________________________ Andrew J. P. Maclean Centre for Autonomous Systems The Rose Street Building J04 The University of Sydney 2006 NSW AUSTRALIA Ph: +61 2 9351 3283 Fax: +61 2 9351 7474 URL: http://www.acfr.usyd.edu.au/ ___________________________________________
On Thu, Mar 19, 2009 at 2:52 AM, Andrew Maclean <andrew.amaclean@gmail.com> wrote: > Two things: > 1) Has the mixed slashes on the certificate file been fixed? Thats a bug in PostgreSQL's libpq library, not pgAdmin. A fix is being discussed though. > 2) With respect to the error: "Error connecting to server: root > certificate file." This was not present in earlier versions of > pgAdminIII, notably 8.3. is this a feature of the new program and if > so are there instructions on how to fix this in windows/linux? I have > only tried windows not linux. By the way this error is not present for > a localhost connection. The error occurs because by default, libpq now tries to verify the SSL certificate presented by the server against a root certificate on the local machine. This is what you probably want of course (because you want to verify that the server is actually one you trust, and you're not getting caught in a man in the middle hack). Because we realised some people may not want to distribute root certificates immediately however, an 'SSL Verify' option has been added to the server dialog so you can specify the behaviour you want. > Overall it is very nice, the SQL Graphical Query builder looks > intuitive and easy to use. Thanks - kudos to Luis Ochoa for that feature! -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
I've been playing with this again this morning and I've noticed the "server status" panel is now much nicer. However one thing that has always tripped me up is that it expects the log_filename to be of the format "postgresql-%Y-%m-%d_%H%M%S.log",but I've always logged into one file for each day, i.e. "postgresql-%Y-%m-%d.log" Is there a setting for this somewhere? Else could we get one, or perhaps even read it from the postgresql.conf settings?
On Thu, Mar 19, 2009 at 9:43 AM, Glyn Astill <glynastill@yahoo.co.uk> wrote:
>
> I've been playing with this again this morning and I've noticed the "server status" panel is now much nicer.
>
> However one thing that has always tripped me up is that it expects the log_filename to be of the format
"postgresql-%Y-%m-%d_%H%M%S.log",but I've always logged into one file for each day, i.e. "postgresql-%Y-%m-%d.log"
>
> Is there a setting for this somewhere? Else could we get one, or perhaps even read it from the postgresql.conf
settings?
This is a limitation in the server. The pg_logdir_ls function needs
the default logfile format to ensure it can reliably figure out the
log date:
if (strcmp(Log_filename, "postgresql-%Y-%m-%d_%H%M%S.log") != 0) ereport(ERROR,
(errcode(ERRCODE_INVALID_PARAMETER_VALUE), (errmsg("the log_filename
parameter
must equal 'postgresql-%%Y-%%m-%%d_%%H%%M%%S.log'"))));
You can still use per-day logs with the default filename of course -
you'll just need to ignore the time part.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--- On Thu, 19/3/09, Dave Page <dpage@pgadmin.org> wrote:
>
> This is a limitation in the server. The pg_logdir_ls
> function needs
> the default logfile format to ensure it can reliably figure
> out the
> log date:
>
> if (strcmp(Log_filename,
> "postgresql-%Y-%m-%d_%H%M%S.log") != 0)
> ereport(ERROR,
>
> (errcode(ERRCODE_INVALID_PARAMETER_VALUE),
> (errmsg("the
> log_filename parameter
> must equal
> 'postgresql-%%Y-%%m-%%d_%%H%%M%%S.log'"))));
>
> You can still use per-day logs with the default filename of
> course -
> you'll just need to ignore the time part.
>
Hmm, that confused me for a second there but doxygen cleared it up.
I see what you mean, I guess I'll just have to rename my logs then and try to overcome the ocd I exhibit at times.
Le jeudi 19 mars 2009 à 11:26:22, Glyn Astill a écrit :
> --- On Thu, 19/3/09, Dave Page <dpage@pgadmin.org> wrote:
> > This is a limitation in the server. The pg_logdir_ls
> > function needs
> > the default logfile format to ensure it can reliably figure
> > out the
> > log date:
> >
> > if (strcmp(Log_filename,
> > "postgresql-%Y-%m-%d_%H%M%S.log") != 0)
> > ereport(ERROR,
> >
> > (errcode(ERRCODE_INVALID_PARAMETER_VALUE),
> > (errmsg("the
> > log_filename parameter
> > must equal
> > 'postgresql-%%Y-%%m-%%d_%%H%%M%%S.log'"))));
> >
> > You can still use per-day logs with the default filename of
> > course -
> > you'll just need to ignore the time part.
>
> Hmm, that confused me for a second there but doxygen cleared it up.
>
> I see what you mean, I guess I'll just have to rename my logs then and try
> to overcome the ocd I exhibit at times.
FYI, I intend to work more on the server status window for next release. The
logfile pane will be reworked to add better understanding of the log_filename
and log_line_prefix parameters. If you have ideas/comments, don't hesitate to
tell me what you need.
--
Guillaume.http://www.postgresqlfr.orghttp://dalibo.com