-Original Message-
From: Kevin Grittner [mailto:kgri...@ymail.com]
Sent: Saturday, June 14, 2014 8:16 PM
To: Khangelani Gama; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Using pg_start_backup() and pg_stop_backup() -
using 9.1.2.2
Khangelani Gama wrote:
> I am doing
On 06/14/2014 06:44 AM, Khangelani Gama wrote:
Hi all
Please help me here.
I would say the best way to help is to figure out what it is you want
out of the master/standby/archive setup before getting into the actual
configuration.
What do you want to do with the standby/archive?
1) Do yo
On 06/14/2014 11:15 AM, Kevin Grittner wrote:
Khangelani Gama wrote:
I am doing the following between master and the backup server
using archive_command,
I'm not sure what that means. Do you mean that while performing
the steps you describe, an archive command was active, copying WAL
files
Khangelani Gama wrote:
> I am doing the following between master and the backup server
> using archive_command,
I'm not sure what that means. Do you mean that while performing
the steps you describe, an archive command was active, copying WAL
files to an archive directory?
> On backup or secon
Hi all
Please help me here.
I am doing the following between master and the backup server using
archive_command,
I am using O/S - Red Hat Enterprise Linux Server release 5.3 (Tikanga)
On backup or secondary server I did the following:
1. Stopped postgres in backup server
On Wed, Jul 17, 2013 at 10:49 AM, John R Pierce wrote:
> On 7/16/2013 6:21 PM, David B Harris wrote:
>>
>> Actually though (if any PostgreSQL developers are paying attention), it
>> might be useful to have a new WAL segment-managing behaviour. With the
>> advent of the replication functionality (w
On 7/16/2013 6:21 PM, David B Harris wrote:
Actually though (if any PostgreSQL developers are paying attention), it
might be useful to have a new WAL segment-managing behaviour. With the
advent of the replication functionality (which is amazing stuff, thanks
so much), I'd expect fewer and fewer i
Yep, my tests were broken :)
Thanks :)
Though it's still possible that the backup would be fine if
wal_keep_segments is high enough - might be good if section 24.3
explicitly mentioned as much.
Actually though (if any PostgreSQL developers are paying attention), it
might be useful to have a new
On Wed Jul 17, 09:16am +0900, Michael Paquier wrote:
> On Wed, Jul 17, 2013 at 8:24 AM, David B Harris
> wrote:
> > On Wed Jul 17, 08:12am +0900, Michael Paquier wrote:
> > 4. In parallel, WAL archiving has copied all the logs from the
> > start of pg_start_backup() through to the en
On Wed, Jul 17, 2013 at 8:24 AM, David B Harris wrote:
> On Wed Jul 17, 08:12am +0900, Michael Paquier wrote:
>> On Tue, Jul 16, 2013 at 11:10 PM, David B Harris
>> wrote:
>> > 4. Copy all logs from start of pg_start_backup() through to when
>> >pg_stop_backup() finished (using the b
On Wed Jul 17, 08:12am +0900, Michael Paquier wrote:
> On Tue, Jul 16, 2013 at 11:10 PM, David B Harris
> wrote:
> > 4. Copy all logs from start of pg_start_backup() through to when
> >pg_stop_backup() finished (using the backup history file, I
> >guess, which I haven't actual
On Tue, Jul 16, 2013 at 11:10 PM, David B Harris wrote:
> Good afternoon all,
>
> I'm trying to use pg_start_backup() and pg_stop_backup() to create
> point-in-time backups. More specifically, I'm trying to use filesystem
> tools (notably rsync or an rsync-like tool) since the production machine
>
Good afternoon all,
I'm trying to use pg_start_backup() and pg_stop_backup() to create
point-in-time backups. More specifically, I'm trying to use filesystem
tools (notably rsync or an rsync-like tool) since the production machine
is on the other end of a (narrow, expensive) pipe. pg_dump is too
e
13 matches
Mail list logo
