On Fri, Sep 16, 2011 at 3:27 AM, marvin.deoliveira
wrote:
> I'll certainly follow your advices.
> The log_truncate_on_rotation parameter is set to on.
> I figured that saves a lot of disk space in this context. this is hurting
> the performance?
That option shouldn't have any impact on performanc
I'll certainly follow your advices.
The log_truncate_on_rotation parameter is set to on.
I figured that saves a lot of disk space in this context. this is hurting
the performance?
-
Marcos Oliveira
And I still haven't found what I'm looking for...
--
View this message in context:
http://post
The dump file is in a different disk than a database.
I need to have this restore finished ( it is about 80% done )
I will have to do it again, but with the changes.
I will return the results to this post.
-
Marcos Oliveira
And I still haven't found what I'm looking for...
--
View this message
On Thu, Sep 15, 2011 at 4:12 PM, marvin.deoliveira
wrote:
> I'm using postgres 9.0.2 32 bits on Debian 5.
> The hardware is a pc with 2 GB RAM, with 2 sata disks. Well, that's what I
> have at the moment.
>
> The restore was started like: pg_restore -U postgres --data-only
> --disable-triggers -v
I'm using postgres 9.0.2 32 bits on Debian 5.
The hardware is a pc with 2 GB RAM, with 2 sata disks. Well, that's what I
have at the moment.
The restore was started like: pg_restore -U postgres --data-only
--disable-triggers -v /bck/.sql -d
The pg_restore shows:
pg_restore: disabling triggers fo
On Thu, Sep 15, 2011 at 3:32 PM, marvin.deoliveira
wrote:
> Hi.
> I'm restoring a database (only rows) that has some tables with 9 millions
> rows and others have even more.
> It's going to slow ( more than 24 hours by now ).
> I'm disabling the triggers but I guess if I drop the indexes it will h
