On Thu, 2008-01-31 at 10:02 -0500, Chander Ganesan wrote:
> Magnus Hagander wrote:
> > On Thu, Jan 31, 2008 at 03:34:05PM +0100, Martijn van Oosterhout wrote:
> >
> >> On Thu, Jan 31, 2008 at 01:28:48PM +, Simon Riggs wrote:
> >>
> >>> That sentence has no place in any discussion about
On Thu, 2008-01-31 at 12:09 -0300, Alvaro Herrera wrote:
> > Simon Riggs wrote:
>
> >> As far as I am concerned, if any Postgres user loses data then we're all
> >> responsible.
>
> Remember, our license says this software is given without any warranty
> whatsoever, implicit or explicit, written
> Simon Riggs wrote:
>> As far as I am concerned, if any Postgres user loses data then we're all
>> responsible.
Remember, our license says this software is given without any warranty
whatsoever, implicit or explicit, written or implied, given or sold,
alive or deceased.
--
Alvaro Herrera
Magnus Hagander wrote:
On Thu, Jan 31, 2008 at 03:34:05PM +0100, Martijn van Oosterhout wrote:
On Thu, Jan 31, 2008 at 01:28:48PM +, Simon Riggs wrote:
That sentence has no place in any discussion about "backup" because the
risk is not just a few transactions, it is a corrupt and in
Simon Riggs wrote:
On Thu, 2008-01-31 at 07:21 -0500, Chander Ganesan wrote:
If you don't mind if you lose some transactions
That sentence has no place in any discussion about "backup" because the
risk is not just a few transactions, it is a corrupt and inconsistent
database from which
On Thu, Jan 31, 2008 at 03:34:05PM +0100, Martijn van Oosterhout wrote:
> On Thu, Jan 31, 2008 at 01:28:48PM +, Simon Riggs wrote:
> > That sentence has no place in any discussion about "backup" because the
> > risk is not just a few transactions, it is a corrupt and inconsistent
> > database f
On Thu, Jan 31, 2008 at 01:28:48PM +, Simon Riggs wrote:
> That sentence has no place in any discussion about "backup" because the
> risk is not just a few transactions, it is a corrupt and inconsistent
> database from which both old and new data would be inaccessible.
Hmm? I thought the whole
On Thu, 2008-01-31 at 07:21 -0500, Chander Ganesan wrote:
> If you don't mind if you lose some transactions
That sentence has no place in any discussion about "backup" because the
risk is not just a few transactions, it is a corrupt and inconsistent
database from which both old and new data would
Simon Riggs wrote:
On Fri, 2008-01-25 at 11:34 +1100, Phillip Smith wrote:
We have a center in Europe who has just started to use PostgreSQL and was
asking me if there are any Symantec product or other products that backup
this type of database.
It doesn't appear to.
The design
AFAIK Dominic needs a plug-in certified by Symantec, and that is not the case.
As you may have read prior to this mail, the common way is to pg_dump
against a file, picking up that file later with BackupExec as a
regular file.
We are currently (www.globant.com) using it that way, no problems at a
PostgreSQL has its own inbuilt mechanism for backing up the database. you can
refer to the postgres manual online for more information.
http://www.postgresql.org/docs/8.2/interactive/backup.html
- Vishal
Subject: [ADMIN] BackupDate: Thu, 24 Jan 2008 14:08:26 -0500From: [EMAIL
PROTECTED]:
On Fri, 2008-01-25 at 11:34 +1100, Phillip Smith wrote:
> > We have a center in Europe who has just started to use PostgreSQL and was
> > asking me if there are any Symantec product or other products that backup
> > this type of database.
>
> It doesn't appear to.
The design of the PITR system a
On Jan 24, 2008 1:08 PM, Dominic Carlucci <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
> We have a center in Europe who has just started to use PostgreSQL and
> was asking me if there are any Symantec product or other products that
> backup this type of database. We presently run VERITAS ver9.1 on
>
> We have a center in Europe who has just started to use PostgreSQL and was
> asking me if there are any Symantec product or other products that backup
> this type of database.
It doesn't appear to. I've just been through the whole rigmarole of
BackupExec for some Windows Servers, and I couldn't f
On Thu, Nov 22, 2007 at 09:14:13AM -0500, Martin Gainty wrote:
>
> Good Morning AndrewI noticed the Vixie cron responds to SIGHUP signalsDo
> you have any suggestions or tutorials on how Postgres would feed these
> event signals to Vixie cron?
Why would Postgres have to tell crond to restart?
A
On Thu, Nov 22, 2007 at 02:59:33PM +0100, Marco Bizzarri wrote:
> Andrew, can you confirm the previous statement? I'm checking on a Debian
> Linux,
> at it seems to be a Vixie Cron, and that feature is described in the man
> page...
If the feature's in your man page, then it works on your system
On Nov 22, 2007 2:53 PM, Andrew Sullivan <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 22, 2007 at 02:28:08PM +0100, Marco Bizzarri wrote:
> >
> > why don't you add a "MAILTO=" at the start of your
> > crontab file, so that you can receive a report of the problem?
>
> Note: check that your cron accepts
On Thu, Nov 22, 2007 at 02:28:08PM +0100, Marco Bizzarri wrote:
>
> why don't you add a "MAILTO=" at the start of your
> crontab file, so that you can receive a report of the problem?
Note: check that your cron accepts such an addition. Many systems now use
Vixie's cron, which does accept that,
On Nov 22, 2007 2:46 PM, Sorin N. Ciolofan <[EMAIL PROTECTED]> wrote:
> Hi Marco!
>
> Thank you for the advice.
>
> I got:
>
> /home/swkm/services/test/backup.sh: line 4: pg_dump: command not found
> updating: mydb_dump_22-11-07.out (stored 0%)
>
> which seems strange
>
>
Try putting the full path
Hi Marco!
Thank you for the advice.
I got:
/home/swkm/services/test/backup.sh: line 4: pg_dump: command not found
updating: mydb_dump_22-11-07.out (stored 0%)
which seems strange
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Marco Bizzarri
Sent: Th
On Nov 22, 2007 2:19 PM, Sorin N. Ciolofan <[EMAIL PROTECTED]> wrote:
> Hello all!
>
> I've a small bash script backup.sh for creating dumps on my Postgre db:
>
> #!/bin/bash
> time=`date '+%d'-'%m'-'%y'`
> cd /home/swkm/services/test
> pg_dump mydb > mydb_dump_$time.o
21 matches
Mail list logo
