[ADMIN] Problem in restore data

Dear All My FC3 is cresh . but i copy my /usr/local/pgsql/data folder how to i use this folder for replace data. Please help me Ramesh Patel System Dept. Banasdairy, Palanpur(B.K.) E-Mail : [EMAIL PROTECTED] Mobile : 94263 91295 ---(end of broadcast)--

[ADMIN] restoring an old database to a new instance -- possible ?

Using PostSQL 7.4 on a linux server, we have one postgres instance with two databases, "gex_runtime" and "mq_geoloc." We had a mishap in which we ran out of disk space. The failure occured in writing to the gex_runtime database. Then an unfortunate slip of an admin's keyboard led to the deletion

[ADMIN] Schema authorization after create database.

Hi I ran into this little astonishment yesterday on 7.4.8. When I create a database connected as the super user using: CREATE DATABASE foo OWNER = foo; The database is indeed owned by user foo, but the automatically created public schema is is owned by the database super user. Should this sche

Re: [ADMIN] Schema authorization after create database.

We have simular behavor: createdb -U user1 mydb pg_restore -U user1 -d mydb filename And the pg_restore complains about the wrong user .I have alwais wolk around this as supreuser. Evgeny Ian FREISLICH wrote: Hi I ran into this little astonishment yesterday on 7.4.8. When I create a databas

[ADMIN] Fwd: Help with rules

Sorry for the repost, but can anyone comment on this, please? -- Forwarded message -- From: Chris Hoover <[EMAIL PROTECTED]> Date: Aug 5, 2005 3:29 PM Subject: Help with rules To: pgsql-admin@postgresql.org I need some help. I was looking at this e-mail (http://archives.postgres

Re: [ADMIN] restoring an old database to a new instance -- possible ?

"Gregory S. Williamson" <[EMAIL PROTECTED]> writes: > Using PostSQL 7.4 on a linux server, we have one postgres instance with two > databases, "gex_runtime" and "mq_geoloc." We had a mishap in which we ran out > of disk space. The failure occured in writing to the gex_runtime database. > Then an

Re: [ADMIN] Schema authorization after create database.

Ian FREISLICH <[EMAIL PROTECTED]> writes: > I ran into this little astonishment yesterday on 7.4.8. When I > create a database connected as the super user using: > CREATE DATABASE foo OWNER = foo; > The database is indeed owned by user foo, but the automatically > created public schema is is own

Re: [ADMIN] Problem in restore data

On Thu, Aug 11, 2005 at 01:03:24PM +0530, Ramesh Patel wrote: > Dear All > > My FC3 is cresh . but i copy my /usr/local/pgsql/data folder > > how to i use this folder for replace data. Install the same version of Postgres in a similar server, do not start it, and drop the "data" folder somewher

[ADMIN] pg_restore

Hi all, We are running postgres 8.03. Getting a dump is no problem on our 6 GB database. However, the restore is a killer, it takes 10 minutes for the dump pg_dump, but over 5 hours for a restore. Is there a way to 'turn off transactions' on the restore to speed things up? I've tried diff

Re: [ODBC] [ADMIN] PG 7.3.4 VS PG 8.0.3 Problem

Hello. I have some bad experience with RHEL 2 and PostgreSQL ODBC. I have seen there a following problem: An ODBC application gets SUCCESS regardless of wether the SQL command succeeded or not! I don't know, wether the psqlodbc behaviour was caused by application's ODBC calling convention, or

Re: [ADMIN] restoring an old database to a new instance -- possible ?

Tom -- Thanks for suggestion. We'll give it a try. Greg W. -Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Thu 8/11/2005 7:07 AM To: Gregory S. Williamson Cc: pgsql-admin@postgresql.org Subject:Re: [ADMIN] restoring an old database to a new instance

Re: [ADMIN] pg_restore

On Thu, Aug 11, 2005 at 15:29:22 -0400, D Kavan <[EMAIL PROTECTED]> wrote: > Hi all, > > We are running postgres 8.03. > > Getting a dump is no problem on our 6 GB database. However, the restore is > a killer, it takes 10 minutes for the dump pg_dump, but over 5 hours for a > restore. Is th

Re: [ADMIN] pg_restore

Bruno Wolff III <[EMAIL PROTECTED]> writes: >> psql dbname < dump_file >> pg_restore -d test_restore_2 -Fc niehs_dump.backup > Some things you can do are to turn off fsync for the restore and not > restore foreign key contsraints and indexes until after the database > has been loaded. pg_dump/pg_

[ADMIN] user postgres

halo i have error like this :  $psql u- abc   error PSQL : FATAL IDENT authentication failed for user “xyz” in  template1 #\c abc : FATAL IDENT authentication failed for user “xyz” previous connection kept   thank's wahyon00. Start your day with Yahoo! - make it your home page