X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 777A353993 for ; Wed, 11 May 2005 17:02:46 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 78655-05 for ; Wed, 11 May 2005 20:02:44 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by svr1.postgresql.org (Postfix) with ESMTP id 4751D5322E for ; Wed, 11 May 2005 17:02:43 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 68so433563wri for ; Wed, 11 May 2005 13:02:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VjXSsctEjtN2RypTlSyf4CohvBgVbfAay/bXC9Nq/w5mFMXiMtVS0MQG6p3H7yh+eb41NWTHr9qpBXq9Z/K7DD80nRVAIUbeL4qATD6QLXZIQYFCuKkTnemeJ77BbSRSRAQkKgYSJNGU1S9mG6Bt/sMfpYfXIH6242zuFL3CO68= Received: by 10.54.76.2 with SMTP id y2mr653100wra; Wed, 11 May 2005 13:02:45 -0700 (PDT) Received: by 10.54.86.16 with HTTP; Wed, 11 May 2005 13:02:45 -0700 (PDT) Message-ID: <33c6269f05051113026338b8ef@mail.gmail.com> Date: Wed, 11 May 2005 16:02:45 -0400 From: Alex Turner Reply-To: Alex Turner To: "GGoshen@axsone.com" Subject: Re: [GENERAL] Storing database in WORM devices Cc: doug@mcnaught.org, pgsql-general@postgresql.org, pgsql-admin@postgresql.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.516 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP, TO_ADDRESS_EQ_REAL X-Spam-Level: X-Archive-Number: 200505/123 X-Sequence-Number: 17552 If you simply put your database tables in their own tablespace, then move that tablespace to a WORM device, I can't see why that wouldn't work as long as you keep all the system tables etc.. on the regular RW tablespace Alex Turner netEconomist On 5/11/05, GGoshen@axsone.com wrote: > I would like to clarify something. > I intend to create the database on a re-writable device (not WORM). At so= me point, when I no longer want to add/modify the database, I plan to copy = it to the WORM device. Then I would like to be able to access the database = on the WORM device for reading purposes only. >=20 > I think that the pg_listener catalog is being written for any user connec= tion. I am not sure whether I could store the system catalogs separated fro= m the application table spaces. >=20 > -----Original Message----- > From: Alex Turner [mailto:armtuk@gmail.com] > Sent: Wednesday, May 11, 2005 3:41 PM > To: Goshen, Galit > Cc: doug@mcnaught.org; pgsql-general@postgresql.org; > pgsql-admin@postgresql.org > Subject: Re: [GENERAL] Storing database in WORM devices >=20 > I think simply initialising the system causes writes in the system > tables and the WAL... >=20 > I'm sure someone more knowledgeable can chime in. >=20 > Alex. Turner > netEconomist >=20 > On 5/11/05, GGoshen@axsone.com wrote: > > Why? Any specific reason that you are aware of ? > > Are there any writes done to the database when read only SQL statements= are issued? > > > > > > -----Original Message----- > > From: Douglas McNaught [mailto:doug@mcnaught.org] > > Sent: Wednesday, May 11, 2005 2:51 PM > > To: Goshen, Galit > > Cc: pgsql-general@postgresql.org; pgsql-admin@postgresql.org > > Subject: Re: [GENERAL] Storing database in WORM devices > > > > writes: > > > > > I would like to store the complete database into a WORM device (Write= Once > > > Read Many). I would like to access this database directly from the WO= RM > > > device and perform read only SQL statements against this device. > > > > > > Does anyone have such installation, or can determine if this is possi= ble? > > > > AFAIK Postgres will not currently run on a read-only filesystem. > > > > -Doug > > > > ---------------------------(end of broadcast)--------------------------= - > > TIP 9: the planner will ignore your desire to choose an index scan if y= our > > joining column's datatypes do not match > > >