You could try removing/disabling your constraints until after the
import/index building.
SET CONSTRAINTS ALL DEFERRED
On Mon, May 9, 2011 at 7:44 AM, Viktor Bojović viktor.bojo...@gmail.comwrote:
Thanx Adrien,
i have tried to skip indexes but constraints rely on them
there is no unique
Hi,
im trying to restore 250GB database, but indexing takes too long, so restore
takes more then 12h.
Is it possible to disable indexing while restoring database?
Thanx in advance
--
---
Viktor Bojović
---
Wherever I go,
It seams there is no option like that in pg_dump or pg_restore. But You
can manualy do it in the dump or with a sed command finding the lines
begining by CREATE INDEX and removing them.
We also have a big database and since postgres 8.4 pg_restore is much
faster with the option --jobs=x
Thanx Adrien,
i have tried to skip indexes but constraints rely on them
there is no unique constraint matching given keys for referenced table
, so i will try to use pg_restore as you have mentioned below.
On Mon, May 9, 2011 at 12:19 PM, adrien ducos adu...@hbs-research.comwrote:
It seams
If the indexes are the issue, you can also try to increase the
maintenance_work_mem during the restore and put it back again as normal
afterwards.
That is what the postgres documentation says about it:
maintenance_work_mem (integer)
Specifies the maximum amount of memory to be used in
Hi All,
I 'm running some db backups tests recovery , using pg_dump d name
--b - F c - db.backup , when I test my restore using pg_restore
dbname and if I run the restore for 2 times in the row for same db
the data gets duplicated in tables is this a feature in pgsql or I 'm
On Sun, 2005-08-21 at 16:16, Dan wrote:
Hello,
We have upgraded our PostgreSQL database version from 7.3.1 (Cygwin)
under Windows 2000 server to v8.03 for windows.
Now we dumped our database (app. size 6 GB) with PgAdmin III with
success. The problem now is that we can’t
Hello,
We have upgraded our PostgreSQL database version from
7.3.1 (Cygwin) under Windows 2000 server to v8.03 for windows.
Now we dumped our database (app. size 6 GB) with
PgAdmin III with success. The problem now is that we cant completely restore
our database with the dump file.
Hi!
I am trying to copy my db from one machine to another .
However since my dump file is pretty big while trying to restore on the
target one
the machine just hangs up - we got an empty black console and no ssh
response.
We think that this is caused by postmaster eating too much memory the
Tsirkin Evgeny [EMAIL PROTECTED] writes:
top - 12:07:46 up 1:06, 2 users, load average: 0.99, 0.93, 0.57
Tasks: 52 total, 3 running, 49 sleeping, 0 stopped, 0 zombie
Cpu(s): 99.7% us, 0.3% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si
Mem: 1035532k total, 364012k used,
Hi guys
I had just recreate database that deleted some
useful data in one of teh table. There's no backup dump badly. But as i know
there a transaction log taht will log everything from beginning, anyone know how
to do a rollback or roll forward?
11 matches
Mail list logo
