Re: [BUGS] Bug #789: Transaction Archival Logging -- Hot Backups

2002-10-07 Thread Jon Watte
ROTECTED]; [EMAIL PROTECTED] > Subject: Re: [BUGS] Bug #789: Transaction Archival Logging -- Hot > Backups > > > > I see in the pg_dump manual page: > >pg_dump makes consistent backups even if the database is >being used concurrently. pg_dump does not block

Re: [BUGS] Bug #789: Transaction Archival Logging -- Hot Backups

2002-10-04 Thread Bruce Momjian
y, we'd > rather pay Oracle lots of money than lose time having to implement it in > the PostgreSQL code :-( > > Cheers, > > / h+ > > > > -Original Message- > > From: Bruce Momjian [mailto:[EMAIL PROTECTED]] > > Sent: Sa

Re: [BUGS] Bug #789: Transaction Archival Logging -- Hot Backups

2002-09-28 Thread Bruce Momjian
I see in the pg_dump manual page: pg_dump makes consistent backups even if the database is being used concurrently. pg_dump does not block other users accessing the database (readers or writers). --

[BUGS] Bug #789: Transaction Archival Logging -- Hot Backups

2002-09-28 Thread pgsql-bugs
Jon Watte ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description Transaction Archival Logging -- Hot Backups Long Description I see no mention of transaction archival logging in the documentation. This means that, even though you sup