Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id BE01F1337BD5 for ; Wed, 23 Mar 2011 07:55:56 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 46363-05 for ; Wed, 23 Mar 2011 10:55:49 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-px0-f174.google.com (mail-px0-f174.google.com [209.85.212.174]) by mail.postgresql.org (Postfix) with ESMTP id E919A1337BCF for ; Wed, 23 Mar 2011 07:55:48 -0300 (ADT) Received: by pxi15 with SMTP id 15so1368301pxi.33 for ; Wed, 23 Mar 2011 03:55:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=iCaNcneTEVYSu0V5rAqQ+AyIWQtVPcCINPnpqyerFaE=; b=E0/nk748F1biA7XzY4WSXIhAYNFtN1uy4nbtemB8jAzne4aGNRECn2JpSQdMVnPAHw bxPjI932hX7gj3aDMMc67lXC42xgtUTV7sgWCNT03FzZolC2m6NFvf1XAbPZVvq19T0G 0x7DnyN954IQ5mzfl2lz9yXk+xB3H2IMGT2Mo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=fY7uojVnUTEf5UAOCztGLdr6dQK6WTRk5Rk3AZRzmfNQlipTdv5pamz8Q0FD5SgU6j UVwkj3NwPQv6FT62+gJ+hzPeNx/L197qZzimhuiu9rIb93ZykISAZBMh0DliA/WpO5hr yqrkE61XGDG/Rl+eG2vTVfqIJEyPOfdXNu0PI= Received: by 10.142.180.3 with SMTP id c3mr5159167wff.101.1300877748407; Wed, 23 Mar 2011 03:55:48 -0700 (PDT) Received: from [172.24.35.132] ([59.162.78.200]) by mx.google.com with ESMTPS id p40sm9932722wfc.5.2011.03.23.03.55.44 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 Mar 2011 03:55:46 -0700 (PDT) Subject: Re: Hot-standby/Reporting database. Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Vibhor Kumar In-Reply-To: <1300483544.6860.48.camel@darkflame.weatherman.net> Date: Wed, 23 Mar 2011 16:28:20 +0530 Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <40A0B8B3-3449-4F37-A930-6F131AAA5CA9@gmail.com> References: <0515F2BB-0522-449C-848B-4E750F4D91BB@pandora.com> <1300483544.6860.48.camel@darkflame.weatherman.net> To: jweatherman91@alumni.wfu.edu X-Mailer: Apple Mail (2.1082) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.589 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201103/212 X-Sequence-Number: 37084 On Mar 19, 2011, at 2:55 AM, John P Weatherman wrote: > I have recently upgraded to Postgres9 and am building a hot standby = for > reporting. Unfortunately, my end users are providing requirements for > 1) real time data replication (which the hot standby does) and 2) the > ability to create temporary tables as part of their reporting jobs > (which is expressly prohibited in a hot standby. >=20 Yes. On Hotstandby you cannot create Tables. > Has anyone run into this already and have an idea for a work around? =20= Looking your requirement, I would recommend to use Slony Replication, = which replicate data from mater to slave and also, gives ability to = create temporary table, without allowing user to tamper/modify the data = of Replicated Tables of (Master).=20 Thanks & Regards, Vibhor Kumar vibhor.aim@gmail.com Blog:http://vibhork.blogspot.com