Fri Sep 25 03:36:02 PDT 2009
- Previous message: [Slony1-general] Slony1 2.0.3-rc2 problem between PostgreSQL 8.3.5 -> 8.4.1
- Next message: [Slony1-general] copying large file won't get replicate
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, I am bulkloading (copying)about 10million of records (total size about 1G) with replication runing. Takes me about 2h30m to load whole data into Master, but after that I give it like another an hour or so to load into my slave ( I only have one slave), but zero record got inserted. I then give it overnight to do its work, which gives almost 20 hours and still nothing happen. I examing the log on Slave and seem no obvious activity has sigh of data inserting. (I have attached part of my log) I do see slony replication behave as records won't show up in slave table until all records got processed then it will load WHOLE records all at once into the table. I observe this by monitoring slave log. This makes me think, before records load on the table physically and while data is in processing, are they temporary storted in the memory and waiting to be load into the table once done with read records from copying? Here is my concern. I copying both 10k and 1million of records with success, but why can't 10Million records? Is this has something to do with my memory size, which loading 10Million of records is too much for my server to handle? I have 512MB memory on both master and slave. -- View this message in context: http://www.nabble.com/copying-large-file-won%27t-get-replicate-tp25609853p25609853.html Sent from the Slony-I -- General mailing list archive at Nabble.com.
- Previous message: [Slony1-general] Slony1 2.0.3-rc2 problem between PostgreSQL 8.3.5 -> 8.4.1
- Next message: [Slony1-general] copying large file won't get replicate
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list