[pgadmin-support] Bug - Rows in Query Output pane fail to grow in height when font size preference size is larger

2011-02-16 Thread Basil Bourque
I'm new to Postgres and pgAdmin -- Where should I report a bug in pgAdmin? I found an annoying cosmetic bug in pgAdmin where the rows in the data grid showing the result of a SQL execution are not re-sized to accommodate a very large font size set in preferences. 1) Set Preferences > Query Tool

Re: [pgadmin-support] dynamic results of a PG_Dump or pg_Restore in the list

2011-02-16 Thread Guillaume Lelarge
Le 16/02/2011 23:13, Doug Easterbrook a écrit : > To Whom it may concern > > PgAdmin is fantastic. Lets just star there. Been using it since 8.2 of > postgres and it is the tool of choice. > > One think I always wanted to ask for as an enhancement is that the backup and > restore functions

Re: [pgadmin-support] 1.12.1 - cannot dump from older server versions

2011-02-16 Thread Guillaume Lelarge
Le 16/02/2011 19:41, rleonanaya a écrit : > > > Guillaume Lelarge-3 wrote: >> >> Le 12/01/2011 18:23, jan-peter.seif...@gmx.de a écrit : >>> Hello, >>> >>> Original-Nachricht Datum: Tue, 11 Jan 2011 23:52:11 +0100 Von: Guillaume Lelarge An: Jan-Peter Seifert >>>

[pgadmin-support] dynamic results of a PG_Dump or pg_Restore in the list

2011-02-16 Thread Doug Easterbrook
To Whom it may concern PgAdmin is fantastic. Lets just star there. Been using it since 8.2 of postgres and it is the tool of choice. One think I always wanted to ask for as an enhancement is that the backup and restore functions for the database display 'live' results in the log window

Re: [pgadmin-support] 1.12.1 - cannot dump from older server versions

2011-02-16 Thread rleonanaya
Guillaume Lelarge-3 wrote: > > Le 12/01/2011 18:23, jan-peter.seif...@gmx.de a écrit : >> Hello, >> >> Original-Nachricht >>> Datum: Tue, 11 Jan 2011 23:52:11 +0100 >>> Von: Guillaume Lelarge >>> An: Jan-Peter Seifert >>> CC: pgadmin-support@postgresql.org >>> Betreff: Re: [

Re: [pgadmin-support] "Invalid byte sequence" message

2011-02-16 Thread Maximilian Tyrtania
Just found this in my log file: ERROR: invalid byte sequence for encoding "UTF8": 0xe3bc64 STATEMENT: SELECT pg_file_read('pg_log/postgresql-2011-02-16_00.log', 10, 5) Still not sure what's going on there. Apparently the contents of the logfile are not valid UTF8 characters. Also

[pgadmin-support] Bug report: Syntax Coloring

2011-02-16 Thread Jakob Egger
Syntax coloring in PgAdmin3 (Version 1.10.3 on MacOS) does not correctly deal with nested comments. Try entering the following in the "Query" window: /* /*NESTED COMMENT*/ THIS IS STILL A COMMENT */ the words "THIS IS STILL A COMMENT" do not have the comment color. The PostgreSQL docs specify