gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Having trouble with gm-restore_database in Mint 17.3


From: Rogerio Luz Coelho
Subject: Re: [Gnumed-devel] Having trouble with gm-restore_database in Mint 17.3 ... Ubuntu 14.04
Date: Sat, 9 Apr 2016 17:27:21 -0300

Seems the gm-bootstrap_server did NOT ask me for a password ...

got this after bootstrap of a new gnumed_v19 in a NEW main cluster
(after pg_dumpcluster / pg_createcluster)

                                List of databases
    Name    |  Owner   | Encoding |   Collate   |    Ctype    |   Access privileges  
------------+----------+----------+-------------+-------------+-----------------------
 gnumed_v18 | gm-dbo   | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 gnumed_v19 | gm-dbo   | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 postgres   | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 template0  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
            |          |          |             |             | postgres=CTc/postgres
 template1  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
            |          |          |             |             | postgres=CTc/postgres
(5 rows)


thx for this help again

Rogerio

2016-04-09 10:10 GMT-03:00 Karsten Hilbert <address@hidden>:
On Sat, Apr 09, 2016 at 03:05:21PM +0200, Karsten Hilbert wrote:

> However, maybe this is easier:

Because

> - setup a brand new cluster
> - bootstrap a new v19 database
> - drop the new v19 database

At this point all the infrastructure needed should be set up
properly and values (say, passwords) known.

Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

_______________________________________________
Gnumed-devel mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/gnumed-devel


reply via email to

[Prev in Thread] Current Thread [Next in Thread]