Re: Optimizing pgsql for read-only access

Steve Lane <slane(at)moyergroup(dot)com> writes:

> Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> writes:
>
> > > Dennis Gearon <gearond(at)fireserve(dot)net> writes:
> > >
> > > This doesn't provide what online backups do, of recovery to the minute of the
> > > crash. And I get nervous having only logical pg_dump output, no backups of the
> > > actual blocks on disk. But is that what everybody does?
> >
> > Gak!! It can never be guaranteed that the "actual blocks on disk"
> > are transactionally consistent. Thus, the pg_dump output is suff-
> > icient.
>
> > Hello all:
> >
> > I'm building a web-based app that is purely a query tool: no data can be
> > added or edited. Postgres is the back end.

What does this have to do with online backups vs pg_dump ?
Please don't follow up to threads with unrelated questions.

In any case you're far more likely to see answers if you post a message
properly as your message won't show up buried inside old threads in people's
mail user agents.

--
greg