On Tue, 2020-06-16 at 00:28 +0200, Peter wrote:
> On Mon, Jun 15, 2020 at 09:46:34PM +0200, Laurenz Albe wrote:
> ! On Mon, 2020-06-15 at 19:00 +0200, Peter wrote:
> ! > And that is one of a couple of likely pitfalls I perceived when
> ! > looking at that new API.
> !
> ! That is a property of my
On Mon, Jun 15, 2020 at 09:46:34PM +0200, Laurenz Albe wrote:
! On Mon, 2020-06-15 at 19:00 +0200, Peter wrote:
! > And that is one of a couple of likely pitfalls I perceived when
! > looking at that new API.
!
! That is a property of my scripts, *not* of the non-exclusive
! backup API...
Then ho
On Sun, Jun 14, 2020 at 03:05:15PM +0200, Magnus Hagander wrote:
! > You can see that all the major attributes (scheduling, error-handling,
! > signalling, ...) of a WAL backup are substantially different to that
! > of any usual backup.
!
! > This is a different *Class* of backup object, therefo
On Mon, 2020-06-15 at 19:00 +0200, Peter wrote:
> And that is one of a couple of likely pitfalls I perceived when
> looking at that new API.
That is a property of my scripts, *not* of the non-exclusive
backup API...
> We could fix that, but that will then get more complicated - and
> people will
On Mon, Jun 15, 2020 at 03:19:29PM +0200, Laurenz Albe wrote:
! On Mon, 2020-06-15 at 14:50 +0200, Peter wrote:
! > ! An example:
! > !
! > ! - Backup #1 calls "pgpre.sh"
! > ! - Backup #1 starts copying files
! > ! - Backup #2 calls "pgpre.sh".
! > ! This will cancel the first backup.
! > ! - B
On Mon, 2020-06-15 at 14:50 +0200, Peter wrote:
> ! An example:
> !
> ! - Backup #1 calls "pgpre.sh"
> ! - Backup #1 starts copying files
> ! - Backup #2 calls "pgpre.sh".
> ! This will cancel the first backup.
> ! - Backup #1 completes copying files.
> ! - Backup #1 calls "pgpost.sh".
> ! It
On Mon, Jun 15, 2020 at 11:44:33AM +0200, Laurenz Albe wrote:
! On Sat, 2020-06-13 at 19:48 +0200, Peter wrote:
! > ! > 4. If, by misconfiguration and/or operator error, the backup system
! > ! > happens to start a second backup. in parallel to the first,
! > ! > then do I correctly assume
On Sat, 2020-06-13 at 19:48 +0200, Peter wrote:
> ! > 4. If, by misconfiguration and/or operator error, the backup system
> ! > happens to start a second backup. in parallel to the first,
> ! > then do I correctly assume, both backups will be rendered
> ! > inconsistent while this may
On Sat, Jun 13, 2020 at 10:13 PM Peter wrote:
> On Thu, Jun 11, 2020 at 10:35:13PM +0200, Magnus Hagander wrote:
> ! > Okay. So lets behave like professional people and figure how that
> ! > can be achieved:
> ! > At first, we drop that WAL requirement, because with WAL archiving
> ! > it is alre
On Thu, Jun 11, 2020 at 10:35:13PM +0200, Magnus Hagander wrote:
! > Okay. So lets behave like professional people and figure how that
! > can be achieved:
! > At first, we drop that WAL requirement, because with WAL archiving
! > it is already guaranteed that an unbroken chain of WAL is always
! >
On Sat, Jun 13, 2020 at 01:53:28PM +0200, Laurenz Albe wrote:
! > I've never seen anybody coding bash - it is strongly shunned in the
! > Berkeley community.
!
! Strange, but then I don't move in these circles.
Never mind.
! > Some Questions:
! > 1. There are explicit error messages in loc-82
On Sat, 2020-06-13 at 05:24 +0200, Peter wrote:
> ! https://github.com/cybertec-postgresql/safe-backup
>
> Ah, thank You, very nice.
>
> I've never seen anybody coding bash - it is strongly shunned in the
> Berkeley community.
Strange, but then I don't move in these circles.
> Some Questions:
On Thu, Jun 11, 2020 at 10:53:15PM +0200, Laurenz Albe wrote:
! On Thu, 2020-06-11 at 22:35 +0200, Magnus Hagander wrote:
! > I believe somebody around that time also wrote a set of bash scripts that
can be used in a pre/post-backup-job combination with the current APIs.
!
! https://github.com/cy
Greetings,
* Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> On 6/9/20 4:15 AM, Stephen Frost wrote:
> >* Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> >>I use pg_backrest, but it does not look promising for running on BSD:
> >>https://fluca1978.github.io/2019/03/04/pgbackrest_FreeBSD.html
On Thu, 2020-06-11 at 22:35 +0200, Magnus Hagander wrote:
> I believe somebody around that time also wrote a set of bash scripts that can
> be used in a pre/post-backup-job combination with the current APIs.
https://github.com/cybertec-postgresql/safe-backup
Yours,
Laurenz Albe
--
Cybertec | ht
On Thu, Jun 11, 2020 at 10:13 PM Peter wrote:
>
> Okay. So lets behave like professional people and figure how that
> can be achieved:
> At first, we drop that WAL requirement, because with WAL archiving
> it is already guaranteed that an unbroken chain of WAL is always
> present in the backup (e
Greetings,
* Peter (p...@citylink.dinoex.sub.org) wrote:
> On Wed, Jun 10, 2020 at 08:32:22AM -0400, Stephen Frost wrote:
> ! > What repo?? I seem to have missed that at first glance.
> !
> ! Yes, pgbackrest has a repo, like most other tools (though they call them
> ! different things... pg_baseb
On Wed, Jun 10, 2020 at 08:32:22AM -0400, Stephen Frost wrote:
! > What repo?? I seem to have missed that at first glance.
!
! Yes, pgbackrest has a repo, like most other tools (though they call them
! different things... pg_basebackup has one though it's not really
! formal).
!
! > Are You inde
On Wed, Jun 10, 2020 at 01:10:36PM +0200, Magnus Hagander wrote:
! > Just having a look at their webpage, something seems to have been updated
! > recently, they now state that they have a new postgres adapter:
! >
! > https://www.bareos.com/en/company_news/postgres-plugin-en1.html
! > Enjoy readi
Greetings,
* Peter (p...@citylink.dinoex.sub.org) wrote:
> On Tue, Jun 09, 2020 at 03:42:48PM -0400, Stephen Frost wrote:
> ! > And then 90% of the things offered here become superfluous, because
> ! > they are already handled site-wide. And then you will have to
> ! > consider integration of both
On Tue, Jun 09, 2020 at 03:42:48PM -0400, Stephen Frost wrote:
! > And then 90% of the things offered here become superfluous, because
! > they are already handled site-wide. And then you will have to
! > consider integration of both pieces - and that will most likely be
! > more work and more erro
On Wed, Jun 10, 2020 at 1:53 AM Peter wrote:
> On Tue, Jun 09, 2020 at 12:34:38PM -0700, Adrian Klaver wrote:
>
> ! The backup solution is?
>
> https://www.bareos.com/
>
> ! Fine rant below. Go forth and work your wonders.
>
> I don't need to, anymore. I did that, for about 20 years - people
> I
On 6/9/20 4:35 PM, Peter wrote:
On Tue, Jun 09, 2020 at 12:34:38PM -0700, Adrian Klaver wrote:
And that can very well be done properly with an incremental filesystem
backup software plus some 20 lines of shellscript.
Read the caveats here:
https://www.postgresql.org/docs/12/backup-file.ht
Greetings,
* Peter (p...@citylink.dinoex.sub.org) wrote:
> On Tue, Jun 09, 2020 at 03:42:48PM -0400, Stephen Frost wrote:
> ! * Peter (p...@citylink.dinoex.sub.org) wrote:
> ! > This professional backup solution also offers support for postgres.
> ! > Sadly, it only covers postgres up to Rel.9, an
On Tue, Jun 09, 2020 at 12:34:38PM -0700, Adrian Klaver wrote:
! The backup solution is?
https://www.bareos.com/
! Fine rant below. Go forth and work your wonders.
I don't need to, anymore. I did that, for about 20 years - people
I used to work for as a consultant (major banks and insurance sho
On 6/9/20 12:02 PM, Peter wrote:
On Tue, Jun 09, 2020 at 01:27:20AM -0400, Tom Lane wrote:
! Adrian Klaver writes:
! > On 6/8/20 7:33 PM, Peter wrote:
! >> That "cp" is usually not synchronous. So there is the possibility
! >> that this command terminates successfully, and reports exitcode zero
On Tue, Jun 09, 2020 at 01:27:20AM -0400, Tom Lane wrote:
! Adrian Klaver writes:
! > On 6/8/20 7:33 PM, Peter wrote:
! >> That "cp" is usually not synchronous. So there is the possibility
! >> that this command terminates successfully, and reports exitcode zero
! >> back to the Postgres, and then
Greetings,
* Peter (p...@citylink.dinoex.sub.org) wrote:
> This professional backup solution also offers support for postgres.
> Sadly, it only covers postgres up to Rel.9, and that piece of software
> wasn't touched in the last 6 or 7 years.
Then it certainly doesn't work with the changes in v12
On 6/9/20 10:55 AM, Peter wrote:
On Mon, Jun 08, 2020 at 09:21:47PM -0700, Adrian Klaver wrote:
!
! On 6/8/20 7:33 PM, Peter wrote:
! >
! > Actually, the affair had some good side: as usual I was checking
! > my own designs first and looking for flaws, and indeed I found one:
! > If you do copy o
On Mon, Jun 08, 2020 at 09:21:47PM -0700, Adrian Klaver wrote:
!
! On 6/8/20 7:33 PM, Peter wrote:
! >
! > Actually, the affair had some good side: as usual I was checking
! > my own designs first and looking for flaws, and indeed I found one:
! > If you do copy out the archive logs not directly
Greetings,
* Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> On 6/9/20 4:15 AM, Stephen Frost wrote:
> >* Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> >>I use pg_backrest, but it does not look promising for running on BSD:
> >>https://fluca1978.github.io/2019/03/04/pgbackrest_FreeBSD.html
On 6/9/20 4:15 AM, Stephen Frost wrote:
Greetings,
* Adrian Klaver (adrian.kla...@aklaver.com) wrote:
I use pg_backrest, but it does not look promising for running on BSD:
https://fluca1978.github.io/2019/03/04/pgbackrest_FreeBSD.html
That's an unfortunately ancient post, really, considering
Greetings,
* Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> I use pg_backrest, but it does not look promising for running on BSD:
> https://fluca1978.github.io/2019/03/04/pgbackrest_FreeBSD.html
That's an unfortunately ancient post, really, considering that
pgbackrest has now been fully rewri
Adrian Klaver writes:
> On 6/8/20 7:33 PM, Peter wrote:
>> That "cp" is usually not synchronous. So there is the possibility
>> that this command terminates successfully, and reports exitcode zero
>> back to the Postgres, and then the Postgres will consider that log
>> being safely away.
> Which
On 6/8/20 7:33 PM, Peter wrote:
Actually, the affair had some good side: as usual I was checking
my own designs first and looking for flaws, and indeed I found one:
If you do copy out the archive logs not directl
Actually, the affair had some good side: as usual I was checking
my own designs first and looking for flaws, and indeed I found one:
If you do copy out the archive logs not directly to ta
36 matches
Mail list logo
