Search Postgresql Archives

Re: [ADMIN] Storing database in WORM devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tom Lane suggested a vacuum freeze (? or something like that) for archival
read only data.  I got the impression the template databases are freeze
dried for freshness (good to the last bit?)  That feature might help as
well in the transition from read-write to read-only.

Rick


                                                                           
             Alex Turner                                                   
             <armtuk@xxxxxxxxx                                             
             >                                                          To 
             Sent by:                  "GGoshen@xxxxxxxxxx"                
             pgsql-admin-owner         <GGoshen@xxxxxxxxxx>                
             @postgresql.org                                            cc 
                                       doug@xxxxxxxxxxxx,                  
                                       pgsql-general@xxxxxxxxxxxxxx,       
             05/11/2005 03:02          pgsql-admin@xxxxxxxxxxxxxx          
             PM                                                    Subject 
                                       Re: [ADMIN]  Storing       
                                       database in WORM devices            
             Please respond to                                             
                Alex Turner                                                
             <armtuk@xxxxxxxxx                                             
                     >                                                     
                                                                           
                                                                           




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@xxxxxxxxxx <GGoshen@xxxxxxxxxx> wrote:
> I would like to clarify something.
> I intend to create the database on a re-writable device (not WORM). At
some 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.
>
> I think that the pg_listener catalog is being written for any user
connection. I am not sure whether I could store the system catalogs
separated from the application table spaces.
>
> -----Original Message-----
> From: Alex Turner [mailto:armtuk@xxxxxxxxx]
> Sent: Wednesday, May 11, 2005 3:41 PM
> To: Goshen, Galit
> Cc: doug@xxxxxxxxxxxx; pgsql-general@xxxxxxxxxxxxxx;
> pgsql-admin@xxxxxxxxxxxxxx
> Subject: Re:  Storing database in WORM devices
>
> I think simply initialising the system causes writes in the system
> tables and the WAL...
>
> I'm sure someone more knowledgeable can chime in.
>
> Alex. Turner
> netEconomist
>
> On 5/11/05, GGoshen@xxxxxxxxxx <GGoshen@xxxxxxxxxx> 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@xxxxxxxxxxxx]
> > Sent: Wednesday, May 11, 2005 2:51 PM
> > To: Goshen, Galit
> > Cc: pgsql-general@xxxxxxxxxxxxxx; pgsql-admin@xxxxxxxxxxxxxx
> > Subject: Re:  Storing database in WORM devices
> >
> > <GGoshen@xxxxxxxxxx> 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
WORM
> > > device and perform read only SQL statements against this device.
> > >
> > > Does anyone have such installation, or can determine if this is
possible?
> >
> > 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
your
> >       joining column's datatypes do not match
> >
>

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend



---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to majordomo@xxxxxxxxxxxxxx)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux