Search Postgresql Archives

slony issues.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux