Re: Opening a recovering DB in for read-only access?
От | Simon Riggs |
---|---|
Тема | Re: Opening a recovering DB in for read-only access? |
Дата | |
Msg-id | 1227286403.7015.88.camel@hp_dx2400_1 обсуждение исходный текст |
Ответ на | Opening a recovering DB in for read-only access? (Philip Warner <pjw@rhyme.com.au>) |
Список | pgsql-hackers |
On Fri, 2008-11-21 at 15:45 +1100, Philip Warner wrote: > Sounds somewhat evil, I know, but I was wondering if it was even > remotely possible with the current design? > > The reason: we are contemplating using pg_standy to create a > warm-standby. It would be a bonus if we would run read-only queries > against this DB to take some of the load off or production servers. > > We currently use slony to provide warm-standby *and* read-only access, > but pg_standby is a great deal more appealing...especially if there was > some way to do read-only access at the same time. Yes, exactly what I'm working on now, currently patch in review. > FWIW, the data would not even need to be completely consistent ... the > kinds of things we are looking at offloading are large summary-type > sequential scans of big tables. Access to inconsistent data has not been agreed. We will only allow access to consistent data with this approach. -- Simon Riggs www.2ndQuadrant.comPostgreSQL Training, Services and Support
В списке pgsql-hackers по дате отправления: