Greg, I am going to gather the figures about our database and I will email to the list, if I am allowed to. Number of tables, number of transactions per day etc. Nothing on our db servers are optimized, hardware wise, the db is on the same volume as logs as the os. I know we have an IO problem because I have been checking it and it has been growing steadily. We must migrate to newer and better optimized hardware. Thank you again Much appreciated. Renato Renato Oliveira Systems Administrator e-mail: renato.oliveira@xxxxxxxxxxx Tel: +44 (0)1763 260811 Fax: +44 (0)1763 262410 http://www.grant.co.uk/ Grant Instruments (Cambridge) Ltd Company registered in England, registration number 658133 Registered office address: 29 Station Road, Shepreth, CAMBS SG8 6GB UK -----Original Message----- From: Scott Marlowe [mailto:scott.marlowe@xxxxxxxxx] Sent: 31 March 2010 09:11 To: Renato Oliveira Cc: Greg Smith; Tino Schwarze; pgsql-admin@xxxxxxxxxxxxxx Subject: Re: Migrate postgres to newer hardware On Wed, Mar 31, 2010 at 1:43 AM, Renato Oliveira <renato.oliveira@xxxxxxxxxxx> wrote: > Greg, > > Thank you very much for your input. > I agree with you and I do understand where you are coming from. > > I do agree that in order to transition without a noticeable downtime the application would need to be built for that. > > Which one works best: bucardo, slony or Londiste? > > I have researched Slony and Bucardo but have not heard of Londiste before. > > How many people are using all three of them and their review have you heard anything about that? I run slony. On our regular db there are about 2000 relations, about 1200 of those are indexes, so slony has to worry about 800 or so relations. It has no problem with that. On another machine that has some 45k relations in addition to the 2000 base relations. That slony instance takes 3.5 hours to run the same create set that takes 2 minutes on the machine with just 2000 relations. Slony should be able to work for you. See if you can schedule it so you start your subscription right when you're entering your lowest throughput window. Your real bottleneck here is that source database with a single hard drive. That's going to limit your speed of subscription by quite a bit. -----Original Message----- P Please consider the environment before printing this email CONFIDENTIALITY: The information in this e-mail and any attachments is confidential. It is intended only for the named recipients(s). If you are not the named recipient please notify the sender immediately and do not disclose the contents to another person or take copies. VIRUSES: The contents of this e-mail or attachment(s) may contain viruses which could damage your own computer system. Whilst Grant Instruments (Cambridge) Ltd has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should therefore carry out your own virus checks before opening the attachment(s). OpenXML: For information about the OpenXML file format in use within Grant Instruments please visit our http://www.grant.co.uk/Support/openxml.html -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
