Re: Scheduled back up (fwd)

From: nolan(at)celery(dot)tssi(dot)com
To: doug(at)mcnaught(dot)org (Doug McNaught)
Cc: pgsql-general(at)postgresql(dot)org (pgsql general list)
Subject: Re: Scheduled back up (fwd)
Date: 2003-07-18 16:40:28
Message-ID: 20030718164028.11811.qmail@celery.tssi.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> > The existing protocols (pg_dump, etc) are largely geared towards
> > DBA-level backups, thus they tend to depend upon backend database
> > access and validation schemes, ie, through .pgpass or pg_hba.conf,
> > as opposed to frontend tools and user-level privilege grants.
>
> What's wrong with \copy in psql?

\copy is fairly limited, especially when compared with the import/export
options in something like Access. This is one of those situation where
the tools that Access provides runs circles around the tools that psql
provides.

Also, what about users who don't have psql access?

More importantly, backups are a back end task, data import/export
is more of a front end task.

If we want to appeal to a wider user base, we have to consider user tool
needs.
--
Mike Nolan

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Richards 2003-07-18 16:47:46 Error Message Using pg_dumpall
Previous Message scott.marlowe 2003-07-18 16:33:41 Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3