Thread: Re: PgAdmin V 1.16.1 Error - Comment on database
PgAdmin V 1.16.1 (on Win7) with Postgres 9.1 Server doesn´t show the Comments on a Database. Neither in SQL Field then in Preferences.
I can overwrite the comments but i still doesn´t show any comment on database but the new set comment can be seen using an older Version of PgAdmin.Am 01.08.2013 08:40, schrieb Oli Noname: > PgAdmin V 1.16.1 (on Win7) with Postgres 9.1 Server doesn´t show the > Comments on a Database. Neither in SQL Field then in Preferences. > > I can overwrite the comments but i still doesn´t show any comment on > database but the new set comment can be seen using an older Version of > PgAdmin. > > Comments on Schemas are shown but not on Databases. Are you sure that only comments on databases are affected? IIRC e.g. comments on functions are affected, too. v1.16.1 is IMO pretty much unusable. users: -When opening the property tab of users they are automatically marked invalid and you can't revoke superuser rights. It would be okay to refuse this for postgres and if no superuser would be left, but this is the case for all superusers. backups: -you don't see which database/schema is being dumped anymore - you have to remember to verify that all objects from the correct database are being dumped in the objects tab. -You have to remember to choose custom format - otherwise you can't restore the backup with pgAdmin III, because it will be in plain text. In the past pgAdmin's default was custom format. (Why not just use psql for restoring plain text backups if server and psql version match anyway? ) -backups on Windows 7 still take a much longer time than calling pg_dump from command line. This has been the case since 1.12 though ... Just use 1.14.3 and PostgreSQL < 9.2 for now ... regards, Peter
On Thu, Aug 1, 2013 at 7:40 AM, Oli Noname <oli835@googlemail.com> wrote: > PgAdmin V 1.16.1 (on Win7) with Postgres 9.1 Server doesn´t show the > Comments on a Database. Neither in SQL Field then in Preferences. > > I can overwrite the comments but i still doesn´t show any comment on > database but the new set comment can be seen using an older Version of > PgAdmin. > > Comments on Schemas are shown but not on Databases. > > Is that a Bug oder a Feature? :-) This has been fixed already for 1.16.2 (or 1.18.0, whichever comes first). -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On Thu, Aug 1, 2013 at 12:13 PM, Jan-Peter Seifert <Jan-Peter.Seifert@gmx.de> wrote: > Am 01.08.2013 08:40, schrieb Oli Noname: >> PgAdmin V 1.16.1 (on Win7) with Postgres 9.1 Server doesn´t show the >> Comments on a Database. Neither in SQL Field then in Preferences. >> >> I can overwrite the comments but i still doesn´t show any comment on >> database but the new set comment can be seen using an older Version of >> PgAdmin. >> >> Comments on Schemas are shown but not on Databases. > > Are you sure that only comments on databases are affected? IIRC e.g. > comments on functions are affected, too. That has been been fixed for 1.16.2. > users: > -When opening the property tab of users they are automatically marked > invalid and you can't revoke superuser rights. It would be okay to > refuse this for postgres and if no superuser would be left, but this is > the case for all superusers. That has also been fixed. > backups: > -you don't see which database/schema is being dumped anymore - you have > to remember to verify that all objects from the correct database are > being dumped in the objects tab. You'll have to explain that one. We display the pg_dump command and output, which includes any database/schema names that the dump is restricted to. The output from pg_dump is not something we control though. > -You have to remember to choose custom format - otherwise you can't > restore the backup with pgAdmin III, because it will be in plain text. > In the past pgAdmin's default was custom format. (Why not just use psql > for restoring plain text backups if server and psql version match anyway? ) I can't find any evidence in the git history that the default has changed, *except* for 1.18.0 in which I've changed it to "Custom". > -backups on Windows 7 still take a much longer time than calling pg_dump > from command line. This has been the case since 1.12 though ... I have no idea why or how that could be the case, and it's not something I've heard elsewhere. Do you use the exact same command in both cases? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Hello, Gesendet: Freitag, 02. August 2013 um 19:45 Uhr Von: "Dave Page" Betreff: Re: [pgadmin-support] PgAdmin V 1.16.1 Error - Comment on database On Thu, Aug 1, 2013 at 12:13 PM, Jan-Peter Seifert > > backups: > > -you don't see which database/schema is being dumped anymore - you have > > to remember to verify that all objects from the correct database are > > being dumped in the objects tab. > You'll have to explain that one. We display the pg_dump command and > output, which includes any database/schema names that the dump is > restricted to. The output from pg_dump is not something we control > though. I've attached the dialogue from 1.12.3. The windows bar says 'Backup Database postgres'. Format 'Compress' is automatically selected. The windows bar in 1.14.3. and 1.16.1 is blank. No format is selected so the dump is always plain text by default. > > -backups on Windows 7 still take a much longer time than calling pg_dump > > from command line. This has been the case since 1.12 though ... > I have no idea why or how that could be the case, and it's not > something I've heard elsewhere. Do you use the exact same command in > both cases? Someone else mentioned this in his reply when I reported this the first time. I guess it does not happen if you use a Windows version older than Windows 7 ... With pgAdmin 1.16.1 it took over 10 minutes to dump the database. I copied the command from pgAdmin ( had to add double quotes because of the blank in the path ): "C:\Program Files\PostgreSQL\9.2\bin\pg_dump.exe" --host localhost --port 5492 --username "postgres" --no-password --verbose--file "D:\1.backup" "database" This took ~ 2:20 minutes in the command line ... No problems with using pgAdmin 1.10.5 and pg_dump 9.2.4 either. The only real difference I see is that the user and the database have no double quotes and that '--no-password' is not beingused in 1.10.5: "C:\Program Files\PostgreSQL\9.2\bin\pg_dump.exe" --host localhost --port 5432 --username postgres --format plain --verbose--file "D:\2.backup" database It happens on Windows 7 64 bit and 32 Bit. No luck with deactivating virus scanners and Aero. Same behavior in Windows XP Mode ... With best regards, Peter
