Re: Scheduled back up (fwd)

From: Doug McNaught <doug(at)mcnaught(dot)org>
To: nolan(at)celery(dot)tssi(dot)com
Cc: pgsql-general(at)postgresql(dot)org (pgsql general list)
Subject: Re: Scheduled back up (fwd)
Date: 2003-07-18 16:02:53
Message-ID: m3fzl32576.fsf@varsoon.wireboard.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

nolan(at)celery(dot)tssi(dot)com writes:

> There is a significant difference between 'backups', which are more of
> a DBA-level task and thus likely to be under the control of someone
> who in a UNIX context has root access or at least DBA shell access, plus
> the ability to schedule cron jobs, and 'exports' or 'imports', which
> are something that an individual user may wish to do with his/her own
> data independent of any database-wide backup schedules.
>
> 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?

-Doug

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Doug McNaught 2003-07-18 16:06:50 Re: Urgent: 10K or more connections
Previous Message scott.marlowe 2003-07-18 15:59:58 Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3