Comments on: Postgres FTW! http://www.ghidinelli.com/2008/12/29/postgres-ftw Thu, 01 Jun 2017 18:51:00 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: charlie arehart http://www.ghidinelli.com/2008/12/29/postgres-ftw/comment-page-1#comment-53224 charlie arehart Tue, 30 Dec 2008 21:20:15 +0000 http://www.ghidinelli.com/?p=491#comment-53224 Hey Brian, you ask about those with experience doing CF and Amazon EC2, etc. I've had Adam Howitt on the CF Meetup a couple of times talking on the topic. You can find them listed either on the meetup recordings page (recordings.coldfusionmeetup.com) or via a search in my UGTV site list of recordings. Here's a URL to go straight to the search results: http://www.carehart.org/ugtv/list.cfm?search=amazon There's one talk there also from an Amazon consultant, but it really wasn't specific to CF. Hope that may help while you await other replies. Hey Brian, you ask about those with experience doing CF and Amazon EC2, etc. I’ve had Adam Howitt on the CF Meetup a couple of times talking on the topic. You can find them listed either on the meetup recordings page (recordings.coldfusionmeetup.com) or via a search in my UGTV site list of recordings. Here’s a URL to go straight to the search results: http://www.carehart.org/ugtv/list.cfm?search=amazon

There’s one talk there also from an Amazon consultant, but it really wasn’t specific to CF. Hope that may help while you await other replies.

]]> By: Tony Brandner http://www.ghidinelli.com/2008/12/29/postgres-ftw/comment-page-1#comment-53222 Tony Brandner Tue, 30 Dec 2008 17:52:37 +0000 http://www.ghidinelli.com/?p=491#comment-53222 A friend points out this as a potentially larger-scale alternative to pgpool - http://www.slony.info He says: "a bit more meatier implementation but pgpool seems pretty sweet for a smaller implementation" Tony A friend points out this as a potentially larger-scale alternative to pgpool – http://www.slony.info

He says: “a bit more meatier implementation but pgpool seems pretty sweet for a smaller implementation”

Tony

]]> By: Zack Steinkamp http://www.ghidinelli.com/2008/12/29/postgres-ftw/comment-page-1#comment-53221 Zack Steinkamp Tue, 30 Dec 2008 17:38:08 +0000 http://www.ghidinelli.com/?p=491#comment-53221 Cool deal Brian. I will be in touch next week then. ;-) Cool deal Brian. I will be in touch next week then. ;-)

]]> By: brian http://www.ghidinelli.com/2008/12/29/postgres-ftw/comment-page-1#comment-53220 brian Tue, 30 Dec 2008 17:32:57 +0000 http://www.ghidinelli.com/?p=491#comment-53220 @Zack - you take time off??! :) I will gladly take a demo - name your date and time and lunch is on me! @Zack – you take time off??! :) I will gladly take a demo – name your date and time and lunch is on me!

]]> By: Zack Steinkamp http://www.ghidinelli.com/2008/12/29/postgres-ftw/comment-page-1#comment-53219 Zack Steinkamp Tue, 30 Dec 2008 17:24:20 +0000 http://www.ghidinelli.com/?p=491#comment-53219 Brian, to ensure a node/instance failure doesn't take your data, create and mount an Elastic Block Store (EBS) volume to house the data. EBS volumes are highly reliable (running on big Hitachi hardware, e.g. http://www.hds.com/products/storage-systems/universal-storage-platform-v.html ), highly performant, and survive the reboot/shutdown/deletion of a machine instance. You can create a backup of your data in only a few seconds (literally) -- just lock your tables, run the command to snapshot the EBS volume, then unlock tables. This is best done on a slave DB machine so as to not interrupt your service. I've found the best AWS setup so far involves provisioning an instance from a base OS image (I use Rightscale's CentOS 5 images), then configure your accounts, software, etc on that instance, then make a new machine image (AMI) from which you clone new machines from. It takes about 30 minutes to create your own AMI. When making a new machine instance, you provision a new EBS volume using your latest data snapshot as a basis (as a DB slave, it should be set up already to connect and catch up to the master) and mount it to the new instance that is made using your custom AMI. Provisioning a new DB slave is then only a couple of steps, and maybe 5 minutes total time. I'm going to be "off" from Jan 5-19, so if you like I can stop by MSRHQ and give you a demo. Brian, to ensure a node/instance failure doesn’t take your data, create and mount an Elastic Block Store (EBS) volume to house the data.

EBS volumes are highly reliable (running on big Hitachi hardware, e.g. http://www.hds.com/products/storage-systems/universal-storage-platform-v.html ), highly performant, and survive the reboot/shutdown/deletion of a machine instance. You can create a backup of your data in only a few seconds (literally) — just lock your tables, run the command to snapshot the EBS volume, then unlock tables. This is best done on a slave DB machine so as to not interrupt your service.

I’ve found the best AWS setup so far involves provisioning an instance from a base OS image (I use Rightscale’s CentOS 5 images), then configure your accounts, software, etc on that instance, then make a new machine image (AMI) from which you clone new machines from. It takes about 30 minutes to create your own AMI.

When making a new machine instance, you provision a new EBS volume using your latest data snapshot as a basis (as a DB slave, it should be set up already to connect and catch up to the master) and mount it to the new instance that is made using your custom AMI.

Provisioning a new DB slave is then only a couple of steps, and maybe 5 minutes total time.

I’m going to be “off” from Jan 5-19, so if you like I can stop by MSRHQ and give you a demo.

]]>