Re: [ADMIN] How add db users from shell script with their passwords?

2008-06-03 Thread Medi Montaseri
You can write a program in say Perl and use create user bob with .options encrypted password x valid until xxx which is pretty much what createuser(1) does. Cheers Medi On Tue, Jun 3, 2008 at 12:54 AM, Илья Скорик [EMAIL PROTECTED] wrote: Dear community, help please. I need to

[ADMIN] How add db users from shell script with their passwords?

2008-06-03 Thread Илья Скорик
Dear community, help please. I need to add some standard users to database together with their standard passwords from a shell script. That the script would not ask to enter passwords manually for each user. How it can be made? How I have understood, createuser comand does not allow to make it?

Re: [ADMIN] How add db users from shell script with their passwords?

2008-06-03 Thread Achilleas Mantzios
Στις Tuesday 03 June 2008 11:28:44 ο/η Medi Montaseri έγραψε: You can write a program in say Perl and use create user bob with .options encrypted password x valid until xxx which is pretty much what createuser(1) does. why not just #!/bin/sh psql -c CREATE USER foo PASSWORD

Re: [ADMIN] UUID generation functions

2008-06-03 Thread Rommel the iCeMAn
But 8.3 still does not generate UUIDs, only stores/compares them This is true, however, only last week I completed a successful pg 8.3 install and during the installation I was able to include UUID generation functions as an option. I now have 10 functions called uuid_something. The ones I

Re: [ADMIN] UUID generation functions

2008-06-03 Thread Hyatt, Gordon
Please see my comments in line. -Original Message- From: [EMAIL PROTECTED] [mailto:pgsql-admin- [EMAIL PROTECTED] On Behalf Of Milen A. Radev Sent: Monday, June 02, 2008 6:24 PM To: pgsql-admin@postgresql.org Subject: Re: [ADMIN] UUID generation functions Milen A. Radev написа:

[ADMIN] transaction status error

2008-06-03 Thread Mark Steben
Hi, I'm running 7.4.5 on a secondary remote database (running 8.2.5 everywhere else) This morning I was vacuuming template1 and the other databases on this machine. The postgres logs indicated that it removed a substantial number of commit logs, Presumably because they were obsolete: The

Re: [ADMIN] transaction status error

2008-06-03 Thread Tom Lane
Mark Steben [EMAIL PROTECTED] writes: Hi, I'm running 7.4.5 on a secondary remote database That release is nearly four years old... A little later when I attempted to vacuum template0 I get the following error: ERROR: could not access status of transaction 2065424697 The 7.4.6 release