-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> We are running PG 8.4.4 on Suse 9 and would like to set up a
> master/slave configuration but have the following requirements:
> - we want to be able to freeze the slave and only force it to update 'on
> demand'
> - we have data in other sch
On Mon, Jul 19, 2010 at 10:49 AM, ENGEMANN, DAYSE wrote:
> How can I create it as the same that I have in the other server?
What you likely want here is the same database name, with the same
encoding and collation. And then the global stuff, like user
accounts.
psql -h olddbserver postgres
\l
"ENGEMANN, DAYSE" wrote:
> How can I create it as the same that I have in the other server?
Well, you could use CREATE DATABASE, and maybe a few REVOKE and/or
GRANT statements. Is there some particular concern you have about
this?
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@
How can I create it as the same that I have in the other server?
-Original Message-
From: Kevin Grittner [mailto:kevin.gritt...@wicourts.gov]
Sent: segunda-feira, 19 de julho de 2010 13:43
To: ENGEMANN, DAYSE; pgsql-admin@postgresql.org
Subject: RE: [ADMIN] How to move a database from HP
"ENGEMANN, DAYSE" wrote:
> pg_dump -h sourcemachine -U sourceuser source_dbname | psql
> target_dbname
>
> Is that?
Yes. You need to enter passwords unless they are specified in
.pgpass or you have some form of authorization which doesn't require
typing a password (for example, trust or iden
Hi Kevin,
Sorry to disturb you.. But I am really new in it...
Let me see if I understood...
pg_dump -h sourcemachine -U sourceuser source_dbname | psql target_dbname
Is that?
The data will be import in the existing db?
-Original Message-
From: Kevin Grittner [mailto:kevin.gritt...@wico
Burgholzer, Robert (DEQ)"
wrote:
> This is really interesting. Is there a way to set the locale on
> the fly for a sort? Having looked at the docs, it appears as if
> the initDB step is the only opportunity to do so.
Starting with 8.4 you can specify it at the database level:
http://www.po
"ENGEMANN, DAYSE" wrote:
> If I use the :
> Origim: pg_dump -Ft -b db_name > file.tar
> Target: pg_restore -d new_db file.tar
>
> The target server has a db, using PGDATA=/postgres, the same in
> the other server... There is any risk to lost any data?
Restoring to a new database should not p
Hi Kevin,
If I use the :
Origim: pg_dump -Ft -b db_name > file.tar
Target: pg_restore -d new_db file.tar
The target server has a db, using PGDATA=/postgres, the same in the other
server... There is any risk to lost any data?
-Original Message-
From: pgsql-admin-ow...@postgresql.org
This is really interesting. Is there a way to set the locale on the fly
for a sort? Having looked at the docs, it appears as if the initDB step
is the only opportunity to do so.
Regards,
r.b.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscriptio
Robert Voinea wrote:
> => show lc_collate;
> lc_collate
> -
> en_US.UTF-8
I'm afraid the order you're seeing is what you're supposed to get
for that collation sequence. In that collation, special characters
(including spaces) are only used as tie-breakers for values which
are
We are running PG 8.4.4 on Suse 9 and would like to set up a master/slave
configuration but have the following requirements:
- we want to be able to freeze the slave and only force it to update 'on demand'
- we have data in other schemas in the slave database that we would like to
preserve
The m
12 matches
Mail list logo
