Re: [ADMIN] Catalog
Travis Smith wrote: There are tools that allow you to reverse engineer schemas.. or to generate ERD's .. visio comes to mind. It works on odbc connections. Schema Spy is a slick tool and is free. Works well with postgres. You can find it at source forge: http://schemaspy.sourceforge.net/ Here is their description: Graphical Database Schema Metadata Browser SchemaSpy is a Java-based tool (requires Java 1.4 or higher) that analyzes the metadata of a schema in a database and generates a visual representation of it in a browser-displayable format. It lets you click through the hierarchy of database tables via child and parent table relationships. The browsing through relationships can occur though HTML links and/or though the graphical representation of the relationships. It's also designed to help resolve the obtuse errors that a database sometimes gives related to failures due to constraints. Cheers, HH -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sergio Gabriel Rodriguez Sent: Wednesday, July 23, 2008 10:32 AM To: pgsql-admin@postgresql.org Subject: [ADMIN] Catalog Hi for all, is possible to get PostgreSQL Catalog EER diagram? where can I get it? regards Sergio Gabriel Rodriguez -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin ___ The information in this email or in any file attached hereto is intended only for the personal and confiden- tial use of the individual or entity to which it is addressed and may contain information that is propri- etary and confidential. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communica- tion is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product. Email trans- mission cannot be guaranteed to be secure or error- free. P6070214 -- H. Hall ReedyRiver Group LLC http://www.reedyriver.com -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
[ADMIN] Upgrade clients when (major) upgrading server?
We have 8.1.3 on our operational and development database servers and will upgrade to 8.3.3 (development) and 8.2.9 (operations) soon. (We will not upgrade both systems' databases now because we've already tested 8.2 on our web server database for the past year, so it's already spent time in development.) I have read through the server upgrade notes, and they seem to be pretty self-explanatory. It's even mentioned how to upgrade the client. And that's where my questions lie. The clients on our workstations were installed when our 8.1.3 was installed, which I was not involved with. When I do psql --version on a client machine, it says 8.0.3. When I do this on the server, I get 8.1.3. Do we need to upgrade the clients? Should we? If so to which version? What is involved with that? That is, other than the note in the upgrade/installation man pages, is there a set of instructions for upgrading the client-side software? If we don't have to upgrade now, when would we have to? Are there any things to watch for I should be aware of? Thanks. Chris -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
[ADMIN] -O not working
I backed up all my databases using: pg_dumpall -O -c -U postgres /tmp/pgalldb2 -O to remove owners on all objects -c to drop databases before recreating them during the restore to prevent duplicate records I restored all the databases with this command psql -U postgres -f /tmp/pgalldb2 postgres I tried to drop a user but was denied with the message, . . . some objects depend on it. Why isn't the -O flag not removing the owner from all objects? Thanks Marc -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] -O not working
On Thu, 2008-07-24 at 10:20 -0700, Marc Fromm wrote: I backed up all my databases using: pg_dumpall -O -c -U postgres /tmp/pgalldb2 -O to remove owners on all objects -c to drop databases before recreating them during the restore to prevent duplicate records I restored all the databases with this command psql -U postgres -f /tmp/pgalldb2 postgres I tried to drop a user but was denied with the message, . . . some objects depend on it. Why isn't the -O flag not removing the owner from all objects? Your problem is likely the -c not the -O. In your target database you have a role that owns objects. You can't drop a role if it owns objects. Joshua D. Drake Marc -- The PostgreSQL Company since 1997: http://www.commandprompt.com/ PostgreSQL Community Conference: http://www.postgresqlconference.org/ United States PostgreSQL Association: http://www.postgresql.us/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Upgrade clients when (major) upgrading server?
On Thu, Jul 24, 2008 at 9:00 AM, Chris Bovitz [EMAIL PROTECTED] wrote: We have 8.1.3 on our operational and development database servers and will upgrade to 8.3.3 (development) and 8.2.9 (operations) soon. (We will not upgrade both systems' databases now because we've already tested 8.2 on our web server database for the past year, so it's already spent time in development.) I have read through the server upgrade notes, and they seem to be pretty self-explanatory. It's even mentioned how to upgrade the client. And that's where my questions lie. The clients on our workstations were installed when our 8.1.3 was installed, which I was not involved with. When I do psql --version on a client machine, it says 8.0.3. When I do this on the server, I get 8.1.3. Do we need to upgrade the clients? Should we? If so to which version? What is involved with that? That is, other than the note in the upgrade/installation man pages, is there a set of instructions for upgrading the client-side software? If we don't have to upgrade now, when would we have to? Are there any things to watch for I should be aware of? From the perspective of libpq it's not a huge deal, but psql needs to match to make the \ commands work properly. Upgrading the client is pretty simple. Remove the old client packages and install the new ones. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
[ADMIN] restoring from pg_dumpall
If I restore all the postgresql databases from pg_dumpall and use the -c to drop databases before restoring them the size of the base directory dramatically increases with each restore (193MB to 355MB to 624MB). If I run vacuumdb, it only drops by a few MB. If I do the long process by: 1. stopping the postmaster 2. deleting all contents in the data folder 3. run initdb -D /var/lib/pgsql/data 4. start the postmaster 5. restore of all databases from the same pg_dumpall the size of the base directory does not balloon. I have searched online for optimized backup and restore procedures for postgresql, so far all I have found are the postgresql.org documents which are a little vague on the subject. I must assume there is a better method than my long process that does not bloat the size of the base directory (the databases) as the -c flag seems to do. Marc -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Upgrade clients when (major) upgrading server?
Scott Marlowe wrote: On Thu, Jul 24, 2008 at 9:00 AM, Chris Bovitz [EMAIL PROTECTED] wrote: We have 8.1.3 on our operational and development database servers and will upgrade to 8.3.3 (development) and 8.2.9 (operations) soon. (We will not upgrade both systems' databases now because we've already tested 8.2 on our web server database for the past year, so it's already spent time in "development.") I have read through the server upgrade notes, and they seem to be pretty self-explanatory. It's even mentioned how to upgrade the client. And that's where my questions lie. The clients on our workstations were installed when our 8.1.3 was installed, which I was not involved with. When I do "psql --version" on a client machine, it says "8.0.3". When I do this on the server, I get "8.1.3". Do we need to upgrade the clients? Should we? If so to which version? What is involved with that? That is, other than the note in the upgrade/installation man pages, is there a set of instructions for upgrading the client-side software? If we don't have to upgrade now, when would we have to? Are there any things to watch for I should be aware of? From the perspective of libpq it's not a huge deal, but psql needs to match to make the \ commands work properly. Upgrading the client is pretty simple. Remove the old client packages and install the new ones. Does it matter which version - 8.3.3 or 8.2.9 - we install on our client boxes? Is the client-side backwards compatible? Or should we install both and have a wrapper for the "psql" script to detect which database we're going to and use the appropriate binaries? Chris
Re: [ADMIN] Upgrade clients when (major) upgrading server?
On Thu, Jul 24, 2008 at 1:51 PM, Chris Bovitz [EMAIL PROTECTED] wrote: Does it matter which version - 8.3.3 or 8.2.9 - we install on our client boxes? Is the client-side backwards compatible? Or should we install both and have a wrapper for the psql script to detect which database we're going to and use the appropriate binaries? psql itself is not backwards / forwards compatible. libpq is. So if you need to talk to 8.2 and 8.3 databases from psql, then it's a good idea to have both. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
