From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | slony issues. |
Date: | 2009-11-07 16:23:55 |
Message-ID: | dcc563d10911070823v6d679b3bj2a7dbeaf7f5c8bf0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I already asked this basic question on the slony mailing lists, but
they seem kinda quiet this week.
So, I've got a database with about 30,000 objects in it, and running
the setaddtable() function is taking about 30 seconds, and spinning a
CPU 100% while doing it. Any suggestions on indexes, or changing
functional costs to get this to run in a more reasonable time. I'm
adding about 600 tables and 200 sequences, and with each table taking
30 seconds it's taking about 5 hours to create a set, which is just
crazy to me. On a much slower machine but without the other 29,000 or
so objects, each table takes around 5 to 10 seconds to add, which is
still long, but not quite as long as on my production server.
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2009-11-07 17:57:05 | Re: slony issues. |
Previous Message | Sam Mason | 2009-11-07 15:21:14 | Re: WAL shipping to two machines (PITR) |