[pgadmin-support] Bug report: Syntax Coloring
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 that comments may be nested, see: http://www.postgresql.org/docs/8.4/static/sql-syntax-lexical.html#SQL-SYNTAX-COMMENTS Best Regards, Jakob Egger -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
Re: [pgadmin-support] "Invalid byte sequence" message
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, after i clicked the message boxes away,
the log files contents appear incomplete in the log viewer (a couple hours
worth of entries are simply missing).
Maximilian Tyrtania Software-Entwicklung
Dessauer Str. 6-7
10969 Berlin
http://www.contactking.de
Am 15.02.2011 um 16:07 schrieb Maximilian Tyrtania:
> Hi again,
>
> i upgraded im pg installation to 9.0.3 (from 8.4.2) and now i'm having
> trouble looking at my log files with pg admin 1.12.2. (on Mac OS 10.6) - on
> every refresh I'd get a messagebox saying:
>
> 2011-02-15 14:28:12 ERROR : ERROR: invalid byte sequence for encoding
> "UTF8": 0xe3b66c
>
> The server runs on Mac OS 10.6, the data is UTF8, and the client connection
> settings are as well.
> Any pointers?
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
Re: [pgadmin-support] 1.12.1 - cannot dump from older server versions
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: [pgadmin-support] 1.12.1 - cannot dump from older server >>> versions >> >> I've compared the calls made by both versions of pgAdmin: >> >> 1.10.5 >> C:\Program Files (x86)\PostgreSQL\8.4\bin\pg_dump.exe --host localhost >> --port 5432 --username postgres --format custom --blobs --verbose --file >> "D:\db.backup" db >> >> >> 1.12.2: >> C:\Program Files (x86)\PostgreSQL\8.4\bin\pg_dump.exe --host localhost >> --port 5432 --username "postgres" --format custom --blobs --verbose >> --file "D:\db.backup" db >> >> There's just a slight difference in that the username gets quoted by >> 1.12.2 >> > Yeah, that's a bug of 1.12.2, but I'm quite sure it doesn't explain the > time difference. Bug fixed BTW. > -- > Guillaume > I'm having the same behavior of Peter... My environment is: - PostgreSQL 9.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (Debian 4.3.2-1.1) 4.3.2, 32-bit - PgAdmin III v.1.12.2 on Win 7 64 bits - A 152 MB Database in UTF8 encoding - use backup of pgAdmin with defaults (any changes made) What I can see in the task manager of Win 7 is that the command pg_dump runs by some seconds and then it closes, then another time it runs by some seconds and then it closes... I think this is what makes the refreshing look of all the desktop and the slow pg_dump process. The only thing that I can assume is that the pg_dump is being made table by table instead of the entire database or something like that, cause, this started after in the PgAdmin has delivered the "object" selector functionality in the backup wizard. Hopefully this could help. Rogelio http://www.blocknetworks.com.mx -- View this message in context: http://postgresql.1045698.n5.nabble.com/1-12-1-cannot-dump-from-older-server-versions-tp3295491p3388207.html Sent from the PostgreSQL - pgadmin support mailing list archive at Nabble.com. -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
[pgadmin-support] dynamic results of a PG_Dump or pg_Restore in the list
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 rather than waiting for the end of the full restore. It's really handy to know where in the process something is, the table being restored, the indexes being created, etc. ...as it happens. it also would give insight to other things on a machine. I often end up running pg_restore/pg_dump in terminal command line so that I can see the ongoing progress and judge how much time I have left to keep myself occupied doing coding while the restore finishes. It does it nicely for a vacuum explain, but then I guess that is results coming back from the database itself, so the implementation of the feature might be different. Doug Easterbrook Arts Management Systems Ltd. mailto:d...@artsman.com http://www.artsman.com Phone (403) 536-1205Fax (403) 536-1210
Re: [pgadmin-support] 1.12.1 - cannot dump from older server versions
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 CC: pgadmin-support@postgresql.org Betreff: Re: [pgadmin-support] 1.12.1 - cannot dump from older server versions >>> >>> I've compared the calls made by both versions of pgAdmin: >>> >>> 1.10.5 >>> C:\Program Files (x86)\PostgreSQL\8.4\bin\pg_dump.exe --host localhost >>> --port 5432 --username postgres --format custom --blobs --verbose --file >>> "D:\db.backup" db >>> >>> >>> 1.12.2: >>> C:\Program Files (x86)\PostgreSQL\8.4\bin\pg_dump.exe --host localhost >>> --port 5432 --username "postgres" --format custom --blobs --verbose >>> --file "D:\db.backup" db >>> >>> There's just a slight difference in that the username gets quoted by >>> 1.12.2 >>> >> Yeah, that's a bug of 1.12.2, but I'm quite sure it doesn't explain the >> time difference. Bug fixed BTW. >> -- >> Guillaume >> > > I'm having the same behavior of Peter... > > My environment is: > - PostgreSQL 9.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (Debian > 4.3.2-1.1) 4.3.2, 32-bit > - PgAdmin III v.1.12.2 on Win 7 64 bits > - A 152 MB Database in UTF8 encoding > - use backup of pgAdmin with defaults (any changes made) > > > What I can see in the task manager of Win 7 is that the command pg_dump runs > by some seconds and then it closes, then another time it runs by some > seconds and then it closes... I think this is what makes the refreshing look > of all the desktop and the slow pg_dump process. > > The only thing that I can assume is that the pg_dump is being made table by > table instead of the entire database or something like that, cause, this > started after in the PgAdmin has delivered the "object" selector > functionality in the backup wizard. > pgAdmin launches pg_dump only once even when you ask it to dump part of the database, table by table. -- Guillaume http://www.postgresql.fr http://dalibo.com -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
Re: [pgadmin-support] dynamic results of a PG_Dump or pg_Restore in the list
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 for the database display 'live' results in the log window > rather than waiting for the end of the full restore. It's really handy to > know where in the process something is, the table being restored, the indexes > being created, etc. ...as it happens. it also would give insight to > other things on a machine. > I would love to be able to show a more continuous progress than what we have now, but it would be a lot harder to do, and would involve hacking PostgreSQL itself. Not something I'll the time to work on in the next months :) > I often end up running pg_restore/pg_dump in terminal command line so that I > can see the ongoing progress and judge how much time I have left to keep > myself occupied doing coding while the restore finishes. > I'm afraid this is the only option left. > It does it nicely for a vacuum explain, but then I guess that is results > coming back from the database itself, so the implementation of the feature > might be different. > You don't have a progress shown here too. So, I don't see what you mean. -- Guillaume http://www.postgresql.fr http://dalibo.com -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
[pgadmin-support] Bug - Rows in Query Output pane fail to grow in height when font size preference size is larger
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 (tab) > Font to a larger size, such as 24 points. Click OK to apply. 2) Quit pgAdmin, to be sure new preferences take effect. Restart pgAdmin. 3) Select Tools > Query Tool, to open an interactive SQL session window. 4) Execute some SQL, such as: select now(); Notice the bug: Row 1 in the Output pane is not tall enough to show the large font size of the text. The text is clipped vertically. While cosmetic, this bug affects: - People doing presentations on overhead projectors where increasing the font size makes reading easier for the audience. - People with a preference for larger fonts, often needed on certain computers screens. - People with visual/sight challenges pgAdmin3 1.12.2 on Mac OS X 10.6.5, installed by Postgres 9.0.x. And thanks to all who work on pgAdmin. It has been very useful to me, and I've found it to be very stable and well-built. --Basil Bourque -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
