A cron job can always do the job using pg_dump/pg_dumpall, in case you need
the incremental backup you can opt for PITR WAL based archive logs...
--
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 2/3/07, Joshua Kramer <[EMAIL PROTECTED]> wrote:
Hello All,
What strategies are people using
Use SIGTERM for killing only one process. You can also use kill -INT. It
sends a query cancel to the backend and will not disturb other processes and
the database server.
--
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 2/3/07, Robert D Oden <[EMAIL PROTECTED]> wrote:
Thank you for the res
On Thu, Feb 01, 2007 at 09:32:22PM -0800, Karthikeyan Sundaram wrote:
> 1) I am using 8.2 version
> 2) My database ise encoded as UTF-8 and client encoding is as "SET
> client_encoding = 'UNICODE';"
> 3) We have a portal that are proposed to accept multibyte. We are using
> PHP modules. Do we n
Have you looked at pg_dump and/or pg_dumpall? That would be the more
common way of performing backups.
I run 2 backup's nightly of our databases:
1) As part of a backup script, call pg_dumpall as the postgres *nix
users and PG user, then pipe the output to a file on a remote server.
2) As a cronjo
Hi,
On Wed, 2007-01-31 at 10:22 -0500, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > I wonder if it isn't time to remove the split tarballs. Do they buy
> > us anything?
>
> Not much except confusion, AFAICS. Marc's still convinced they're
> helpful though .
AFAIR, those ta
Hello,
On Fri, 2007-02-02 at 06:08 -0800, Manish Pillai wrote:
> [EMAIL PROTECTED] init.d]# ./postgresql restart
> Stopping postgresql service: [FAILED]
> Starting postgresql service: [FAILED]
> [EMAIL PROTECTED] init.d]#
>
>
After takin a swig o' Arrakan spice grog, [EMAIL PROTECTED] (Joshua Kramer)
belched out:
> Hello All,
>
> What strategies are people using for automated, script-based backup of
> databases? There are a few I can think of:
>
> 1. Create a "db_backup" unix user and a "db_backup" pgsql user. Grant
