On 2020-06-21 17:35:41 -0500, Ron wrote:
> On 6/21/20 10:45 AM, Peter J. Holzer wrote:
> > On 2020-06-21 10:32:16 -0500, Ron wrote:
> > > On 6/21/20 8:28 AM, Peter J. Holzer wrote:
> > > > To make a full backup with the "new" (non-exclusive) API, a software
> > > > must do the following
> > > >
>
On 6/21/20 10:45 AM, Peter J. Holzer wrote:
On 2020-06-21 10:32:16 -0500, Ron wrote:
On 6/21/20 8:28 AM, Peter J. Holzer wrote:
To make a full backup with the "new" (non-exclusive) API, a software
must do the following
1. open a connection to the database
2. invoke pg_start_backup('label', fa
On 2020-06-21 10:32:16 -0500, Ron wrote:
> On 6/21/20 8:28 AM, Peter J. Holzer wrote:
> > To make a full backup with the "new" (non-exclusive) API, a software
> > must do the following
> >
> > 1. open a connection to the database
> >
> > 2. invoke pg_start_backup('label', false, false) in the con
Peter,
I don't understand that last step "5. copy the result from the previous step
to the backup medium." It seems to be a duplication of "3. copy the
contents of the data directory to the backup medium".
On 6/21/20 8:28 AM, Peter J. Holzer wrote:
This is inspired by the thread with the su
This is inspired by the thread with the subject "Something else about
Redo Logs disappearing", but since that thread is already quite long,
since I have lost track what exactly "Peter"'s problem is and since his
somewhat belligerent tone makes it unappealing to reread the whole
thread I'll attempt
