postgres equivalent's

[Nick Estes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> /_> mysqlshow
> /_
> /_If you tell me what it does, I'm sure I could tell you the equivalent (-=
> /_
>
> mysqlshow displays a list of all databases on the server.

\l inside psql will do the trick there.


> I did read an article last night where the author gave
> a really nice comparison...wished I would have saved the URL.
> One thing he mentioned was that when Postgres went down,
> it goes does hard. Corrupted db files/indexes/etc in Postgres
> are not fun....which leads me to my last command question:

It's been a long time since I've had any trouble with postgres after a
crash.  I've never had postgres itsself die on me, but there's always the
occasion when there's a power outage or something.  In those cases, I have
had some trouble with the write ahead logging, but that was a couple
releases ago; not sure if I've just been lucky since then, or if postgres
can recover more gracefully these days...  If that should happen tho,
you'll probably want to read the manpage for pg_resetxlog which will take
care of that corruption for you.


> In mysql there is a program called mysqldump, which I use
> each night to backup all of my databases. It simply dumps
> the contents of the database to a sql file that can be read back in.
>
> Postgres equivalent?

pg_dump, pg_dumpall, and of course, you wouldn't want to forget
pg_restore... (-=

	--Nick

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: pgpenvelope 2.10.2 - http://pgpenvelope.sourceforge.net/

iD8DBQE+65Scv+hjYTGg7s4RAn21AJ9MzOI65AC95Q3BJUnJIvQckDxAAwCeNg/A
DKhqD8fl0vqkH5AW6UKxaug=
=DPY2
-----END PGP SIGNATURE-----