Received: from yoyo.poznan.mtl.pl (IDENT:root@yoyo.poznan.mtl.pl [212.160.241.173]) by hub.org (8.10.1/8.10.1) with ESMTP id e93C4dr19502 for ; Tue, 3 Oct 2000 08:04:39 -0400 (EDT) Received: (from mazek@localhost) by yoyo.poznan.mtl.pl (8.9.3/8.9.3) id OAA32579 for pgsql-sql@postgresql.org; Tue, 3 Oct 2000 14:01:00 +0200 Date: Tue, 3 Oct 2000 14:01:00 +0200 From: Marcin Mazurek To: pgsql-sql@postgresql.org Subject: Re: grant select on ALL(?) to dbuser; Message-ID: <20001003140100.C32413@poznan.mtl.pl> Mail-Followup-To: pgsql-sql@postgresql.org References: <20001003113653.A30185@poznan.mtl.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: ; from alligator@all.ee on Tue, Oct 03, 2000 at 03:01:30PM +0300 Organization: Multinet S.A. X-Archive-Number: 200010/18 Antti Linno (alligator@all.ee) napisał: > Hm, I usually use > pg_dump -f smthng.out dbname -u > after that program asks for username and password, > there were some possibilities within postgres too, but you can find them > yourself. And why not to dump all data as superuser, that way u have no > problems with privileges at all. i want to do it via cron, and rather not user any superusers, except for this it whould by nice to know how to do it not only for pg_dump:) maz Marcin Mazurek -- Kierownik Działu Systemowego MULTINET SA o/Poznan http://www.multinet.pl/