#barman — Public Fediverse posts

https://www.europesays.com/cz/90577/ Vlachynský: Brno versus Praha? Srovnávání barů je zbytečné. Že Gen Z pije méně, je mýtus #4pokoje #Alkohol #bar #barman #Brno #BrnoCocktailWeek #CestovníRuchAVolnočasovýPrůmysl #drink #ekonomika #hobby #Instagram #JanVlachynský #koktejl #KterýNeexistuje #nápoj #ObchodAFinance #Prague #PragueCocktailWeek #Praha #ProduktyASlužby #ProstoryProVolnočasovéAktivity #SuperPandaCircus #Volnýčas #Whiskáč #ZájemOJídloAPití #životníStylAVolnýčas

In case you were looking for a step-by-step guide for setting up a #CloudNativePG replica cluster using the #Barman Cloud Plugin for backups and WAL archiving... look no further: https://www.enterprisedb.com/blog/deployment-postgresql-replica-cluster-barman-cloud-plugin-cloudnativepg-part-1 #PostgreSQL #Kubernetes #CNPG

In case you were looking for a step-by-step guide for setting up a #CloudNativePG replica cluster using the #Barman Cloud Plugin for backups and WAL archiving... look no further: https://www.enterprisedb.com/blog/deployment-postgresql-replica-cluster-barman-cloud-plugin-cloudnativepg-part-1 #PostgreSQL #Kubernetes #CNPG

In case you were looking for a step-by-step guide for setting up a #CloudNativePG replica cluster using the #Barman Cloud Plugin for backups and WAL archiving... look no further: https://www.enterprisedb.com/blog/deployment-postgresql-replica-cluster-barman-cloud-plugin-cloudnativepg-part-1 #PostgreSQL #Kubernetes #CNPG

In case you were looking for a step-by-step guide for setting up a #CloudNativePG replica cluster using the #Barman Cloud Plugin for backups and WAL archiving... look no further: https://www.enterprisedb.com/blog/deployment-postgresql-replica-cluster-barman-cloud-plugin-cloudnativepg-part-1 #PostgreSQL #Kubernetes #CNPG

Barman – Backup and Recovery Manager for PostgreSQL

https://github.com/EnterpriseDB/barman

#HackerNews #Barman #PostgreSQL #Backup #Recovery #Database #Admin #Tools

Herramientas y utensilios de coctelería que no pueden faltar en tu home bar https://www.vinetur.com/2026030396985/herramientas-y-utensilios-de-cocteleria-que-no-pueden-faltar-en-tu-home-bar.html?utm_source=dlvr.it&utm_medium=mastodon #Coctelería #HomeBar #Barman #UtensiliosDeCocktail #cocteles

Herramientas y utensilios de coctelería que no pueden faltar en tu home bar https://www.vinetur.com/2026030396985/herramientas-y-utensilios-de-cocteleria-que-no-pueden-faltar-en-tu-home-bar.html?utm_source=dlvr.it&utm_medium=mastodon #Coctelería #HomeBar #Barman #UtensiliosDeCocktail #cocteles

ADORO IL GENIO - IMPRESCINDIBILI

Ogni #barman ha i suoi #segreti...

#adoroilgenio #28dicembre #bar #comicart #comics #fumetto #fumetti #fantasy #vignette #vignettedivertenti #cocktail #drink #eggnogg #ragazzi #natale #natale2025 #vov #uova #ricetta #ricette #ricettasegreta

ADORO IL GENIO - IMPRESCINDIBILI

Ogni #barman ha i suoi #segreti...

#adoroilgenio #28dicembre #bar #comicart #comics #fumetto #fumetti #fantasy #vignette #vignettedivertenti #cocktail #drink #eggnogg #ragazzi #natale #natale2025 #vov #uova #ricetta #ricette #ricettasegreta

ADORO IL GENIO - IMPRESCINDIBILI

Ogni #barman ha i suoi #segreti...

#adoroilgenio #28dicembre #bar #comicart #comics #fumetto #fumetti #fantasy #vignette #vignettedivertenti #cocktail #drink #eggnogg #ragazzi #natale #natale2025 #vov #uova #ricetta #ricette #ricettasegreta

ADORO IL GENIO - IMPRESCINDIBILI

Ogni #barman ha i suoi #segreti...

#adoroilgenio #28dicembre #bar #comicart #comics #fumetto #fumetti #fantasy #vignette #vignettedivertenti #cocktail #drink #eggnogg #ragazzi #natale #natale2025 #vov #uova #ricetta #ricette #ricettasegreta

ADORO IL GENIO - IMPRESCINDIBILI

Ogni #barman ha i suoi #segreti...

#adoroilgenio #28dicembre #bar #comicart #comics #fumetto #fumetti #fantasy #vignette #vignettedivertenti #cocktail #drink #eggnogg #ragazzi #natale #natale2025 #vov #uova #ricetta #ricette #ricettasegreta

𝗕𝗮𝗿𝗺𝗮𝗻 𝗙𝗶𝗿𝘀𝘁 𝗗𝗮𝘁𝗲𝘀 𝘃𝗶𝗻𝗱𝘁 𝗵𝗲𝘁 '𝘀𝗻𝗲𝘂 𝗲𝗻 𝘁𝗿𝗶𝗲𝘀𝘁' 𝗱𝗮𝘁 𝗽𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗮 𝘀𝘁𝗼𝗽𝘁

Jeremy Zijlstra, de barman van het BNNVARA-programma First Dates, vindt het "sneu en triest" dat het programma stopt. In een gesprek met het ANP zegt hij het "pittig" te vinden dat het programma stopt.

https://www.rtl.nl/boulevard/artikel/5540736/barman-first-dates-vindt-het-sneu-en-triest-dat-programma-stopt

#Barman #FirstDates #Programma

Tomorrow at #PGConfEU: Martín Marqués and Giulio Calacoci walk through how the Barman project grew with the Postgres community and where backup innovation is headed next.

They’ll also share how anyone can get involved, from contributing code to testing and documentation. Don’t miss their talk on Wednesday, Oct 22 at 14:45 (Room Alfa).
#PostgreSQL #EDBPostgresAI #Barman #Backup #OpenSource #PostgresCommunity

𝗙𝗶𝗿𝘀𝘁 𝗱𝗮𝘁𝗲𝘀 𝗸𝗶𝗲𝘀𝘁 𝗼𝗽𝘃𝗼𝗹𝗴𝗲𝗿 𝗯𝗮𝗿𝗺𝗮𝗻 𝗩𝗶𝗰𝘁𝗼𝗿 𝗔𝗯𝗲𝗹𝗻 𝗶𝗻 𝗻𝗶𝗲𝘂𝘄𝗲 𝗿𝗲𝗲𝗸𝘀

Het nieuwe seizoen van het datingprogramma First Dates gaat op 15 september van start. Dat heeft BNNVARA woensdag laten weten. De eerste week zal er aandacht zijn voor de opvolger van barman Victor Abeln. Elke aflevering neemt een andere barman of barvrouw plaats in het restaurant van First...

https://www.rtl.nl/boulevard/artikel/5526472/first-dates-kiest-opvolger-barman-victor-abeln-nieuwe-reeks

#FirstDates #opvolger #barman

Barman woes on OVH

So, due to a cascade of Barman’s errors and corrupted backups due to running out of backup space, I had to pretty much clear out my Barman backup storage.

After resetting everything, however, I was not able to make a full backup, because Barman was not able to receive write-ahead logs from PostgreSQL.

2025-06-04 22:00:21,209 [523687] barman.cli ERROR: [Errno 5] Input/output error: '/backup/barman/pg/wals/00000001000000CD/00000001000000CD00000009.tmp'
See log file for more details.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/barman/cli.py", line 2390, in main
    args.func(args)
  File "/usr/lib/python3/dist-packages/barman/cli.py", line 1600, in archive_wal
    server.archive_wal()
  File "/usr/lib/python3/dist-packages/barman/server.py", line 2651, in archive_wal
    self.backup_manager.archive_wal(verbose)
  File "/usr/lib/python3/dist-packages/barman/backup.py", line 847, in archive_wal
    archiver.archive(verbose)
  File "/usr/lib/python3/dist-packages/barman/wal_archiver.py", line 213, in archive
    self.archive_wal(compressor, wal_info)
  File "/usr/lib/python3/dist-packages/barman/wal_archiver.py", line 356, in archive_wal
    shutil.copystat(src_file, tmp_file)
  File "/usr/lib/python3.12/shutil.py", line 388, in copystat
    _copyxattr(src, dst, follow_symlinks=follow)
  File "/usr/lib/python3.12/shutil.py", line 338, in _copyxattr
    os.setxattr(dst, name, value, follow_symlinks=follow_symlinks)
OSError: [Errno 5] Input/output error: '/backup/barman/pg/wals/00000001000000CD/00000001000000CD00000009.tmp'

Input/output error? That’s odd, but the stacktrace tells us a lot, as from the function name (os.setxattr), we can deduce that it’s trying to set xattrs on our WAL files. The underlying storage for my backups is OVH’s Backup Storage, accessible over NFS. And NFS, for most of its life, was not able to support xattrs even if the underlying filesystem does. The support has been added to NFS 4.2, while OVH (still) uses 4.1.

So, how to fix this?

Initially, I thought of downgrading Barman, because things had worked before. But that did not help, and so I had to go digging into the source code (which was painful as I am not a Python guy).

# Perform the real filesystem operation with the xlogdb lock taken.            # This makes the operation atomic from the xlogdb file POV            with self.server.xlogdb("a") as fxlogdb:                # If the content has changed, it means the file was either compressed                # or encrypted or both. In this case, we need to update its metadata                if content_changed:                    shutil.copystat(src_file, current_file)                    stat = os.stat(current_file)                    wal_info.size = stat.st_size

So, if content_changed is true, we use copystat from shutil.py, which copies xattrs from the original file.

# If the bits of the file has changed e.g. due to compression or encryption            content_changed = False            # Compress the file if not already compressed            if compressor and not wal_info.compression:                compressor.compress(src_file, tmp_file)                files_to_remove.append(current_file)                current_file = tmp_file                content_changed = True                wal_info.compression = compressor.compression            # Encrypt the file            if encryption:                encrypted_file = encryption.encrypt(current_file, dst_dir)                files_to_remove.append(current_file)                current_file = encrypted_file                wal_info.encryption = encryption.NAME                content_changed = True

Ah, so therein lies the rub: Barman assumes that it needs to do this if the content is either being compressed or encrypted. And it just so happens that I’ve also enabled GZIP compression so as not to run out of space again. Well, we have to deal with this the old-fashioned way (by lowering the retention policy). After disabling compression, Barman was able to make backups again.

Hope this helps someone, because it sure as fuck would’ve helped me.

#Barman #lighthearted #NFS #NFSv4 #OVH #pgsql #PostgreSQL #SelfHosting

Barman woes on OVH

So, due to a cascade of Barman’s errors and corrupted backups due to running out of backup space, I had to pretty much clear out my Barman backup storage.

After resetting everything, however, I was not able to make a full backup, because Barman was not able to receive write-ahead logs from PostgreSQL.

2025-06-04 22:00:21,209 [523687] barman.cli ERROR: [Errno 5] Input/output error: '/backup/barman/pg/wals/00000001000000CD/00000001000000CD00000009.tmp'
See log file for more details.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/barman/cli.py", line 2390, in main
    args.func(args)
  File "/usr/lib/python3/dist-packages/barman/cli.py", line 1600, in archive_wal
    server.archive_wal()
  File "/usr/lib/python3/dist-packages/barman/server.py", line 2651, in archive_wal
    self.backup_manager.archive_wal(verbose)
  File "/usr/lib/python3/dist-packages/barman/backup.py", line 847, in archive_wal
    archiver.archive(verbose)
  File "/usr/lib/python3/dist-packages/barman/wal_archiver.py", line 213, in archive
    self.archive_wal(compressor, wal_info)
  File "/usr/lib/python3/dist-packages/barman/wal_archiver.py", line 356, in archive_wal
    shutil.copystat(src_file, tmp_file)
  File "/usr/lib/python3.12/shutil.py", line 388, in copystat
    _copyxattr(src, dst, follow_symlinks=follow)
  File "/usr/lib/python3.12/shutil.py", line 338, in _copyxattr
    os.setxattr(dst, name, value, follow_symlinks=follow_symlinks)
OSError: [Errno 5] Input/output error: '/backup/barman/pg/wals/00000001000000CD/00000001000000CD00000009.tmp'

Input/output error? That’s odd, but the stacktrace tells us a lot, as from the function name (os.setxattr), we can deduce that it’s trying to set xattrs on our WAL files. The underlying storage for my backups is OVH’s Backup Storage, accessible over NFS. And NFS, for most of its life, was not able to support xattrs even if the underlying filesystem does. The support has been added to NFS 4.2, while OVH (still) uses 4.1.

So, how to fix this?

Initially, I thought of downgrading Barman, because things had worked before. But that did not help, and so I had to go digging into the source code (which was painful as I am not a Python guy).

# Perform the real filesystem operation with the xlogdb lock taken.            # This makes the operation atomic from the xlogdb file POV            with self.server.xlogdb("a") as fxlogdb:                # If the content has changed, it means the file was either compressed                # or encrypted or both. In this case, we need to update its metadata                if content_changed:                    shutil.copystat(src_file, current_file)                    stat = os.stat(current_file)                    wal_info.size = stat.st_size

So, if content_changed is true, we use copystat from shutil.py, which copies xattrs from the original file.

# If the bits of the file has changed e.g. due to compression or encryption            content_changed = False            # Compress the file if not already compressed            if compressor and not wal_info.compression:                compressor.compress(src_file, tmp_file)                files_to_remove.append(current_file)                current_file = tmp_file                content_changed = True                wal_info.compression = compressor.compression            # Encrypt the file            if encryption:                encrypted_file = encryption.encrypt(current_file, dst_dir)                files_to_remove.append(current_file)                current_file = encrypted_file                wal_info.encryption = encryption.NAME                content_changed = True

Ah, so therein lies the rub: Barman assumes that it needs to do this if the content is either being compressed or encrypted. And it just so happens that I’ve also enabled GZIP compression so as not to run out of space again. Well, we have to deal with this the old-fashioned way (by lowering the retention policy). After disabling compression, Barman was able to make backups again.

Hope this helps someone, because it sure as fuck would’ve helped me.

#Barman #lighthearted #NFS #NFSv4 #OVH #pgsql #PostgreSQL #SelfHosting

Barman woes on OVH

So, due to a cascade of Barman’s errors and corrupted backups due to running out of backup space, I had to pretty much clear out my Barman backup storage.

After resetting everything, however, I was not able to make a full backup, because Barman was not able to receive write-ahead logs from PostgreSQL.

2025-06-04 22:00:21,209 [523687] barman.cli ERROR: [Errno 5] Input/output error: '/backup/barman/pg/wals/00000001000000CD/00000001000000CD00000009.tmp'
See log file for more details.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/barman/cli.py", line 2390, in main
    args.func(args)
  File "/usr/lib/python3/dist-packages/barman/cli.py", line 1600, in archive_wal
    server.archive_wal()
  File "/usr/lib/python3/dist-packages/barman/server.py", line 2651, in archive_wal
    self.backup_manager.archive_wal(verbose)
  File "/usr/lib/python3/dist-packages/barman/backup.py", line 847, in archive_wal
    archiver.archive(verbose)
  File "/usr/lib/python3/dist-packages/barman/wal_archiver.py", line 213, in archive
    self.archive_wal(compressor, wal_info)
  File "/usr/lib/python3/dist-packages/barman/wal_archiver.py", line 356, in archive_wal
    shutil.copystat(src_file, tmp_file)
  File "/usr/lib/python3.12/shutil.py", line 388, in copystat
    _copyxattr(src, dst, follow_symlinks=follow)
  File "/usr/lib/python3.12/shutil.py", line 338, in _copyxattr
    os.setxattr(dst, name, value, follow_symlinks=follow_symlinks)
OSError: [Errno 5] Input/output error: '/backup/barman/pg/wals/00000001000000CD/00000001000000CD00000009.tmp'

Input/output error? That’s odd, but the stacktrace tells us a lot, as from the function name (os.setxattr), we can deduce that it’s trying to set xattrs on our WAL files. The underlying storage for my backups is OVH’s Backup Storage, accessible over NFS. And NFS, for most of its life, was not able to support xattrs even if the underlying filesystem does. The support has been added to NFS 4.2, while OVH (still) uses 4.1.

So, how to fix this?

Initially, I thought of downgrading Barman, because things had worked before. But that did not help, and so I had to go digging into the source code (which was painful as I am not a Python guy).

# Perform the real filesystem operation with the xlogdb lock taken.            # This makes the operation atomic from the xlogdb file POV            with self.server.xlogdb("a") as fxlogdb:                # If the content has changed, it means the file was either compressed                # or encrypted or both. In this case, we need to update its metadata                if content_changed:                    shutil.copystat(src_file, current_file)                    stat = os.stat(current_file)                    wal_info.size = stat.st_size

So, if content_changed is true, we use copystat from shutil.py, which copies xattrs from the original file.

# If the bits of the file has changed e.g. due to compression or encryption            content_changed = False            # Compress the file if not already compressed            if compressor and not wal_info.compression:                compressor.compress(src_file, tmp_file)                files_to_remove.append(current_file)                current_file = tmp_file                content_changed = True                wal_info.compression = compressor.compression            # Encrypt the file            if encryption:                encrypted_file = encryption.encrypt(current_file, dst_dir)                files_to_remove.append(current_file)                current_file = encrypted_file                wal_info.encryption = encryption.NAME                content_changed = True

Ah, so therein lies the rub: Barman assumes that it needs to do this if the content is either being compressed or encrypted. And it just so happens that I’ve also enabled GZIP compression so as not to run out of space again. Well, we have to deal with this the old-fashioned way (by lowering the retention policy). After disabling compression, Barman was able to make backups again.

Hope this helps someone, because it sure as fuck would’ve helped me.

#Barman #lighthearted #NFS #NFSv4 #OVH #pgsql #PostgreSQL #SelfHosting

Tommy dreams, #barman à Montpellier, accueille le jeune #gay Even Canaillou. Au moment de la fermeture de ce #bar gay, ces deux beaux mecs vont vivre des moments chauds et érotiques dans cette vidéo gay très hot. A lire ici --> https://wp.me/pbyKZP-16op #evencanaillou #beauxmecs #beaucul #beauxgosses #gorgeprofonde #males #lieuxpublics #GrosseBite

Commission I made for @rengaaraz.bsky.social‬. Fancy a drink, sweetheart?
#furry #furryart #commission #dragon #derg #barman #smirk

Commission I made for @rengaaraz.bsky.social‬. Fancy a drink, sweetheart?
#furry #furryart #commission #dragon #derg #barman #smirk

Commission I made for @rengaaraz.bsky.social‬. Fancy a drink, sweetheart?
#furry #furryart #commission #dragon #derg #barman #smirk

Commission I made for @rengaaraz.bsky.social‬. Fancy a drink, sweetheart?
#furry #furryart #commission #dragon #derg #barman #smirk

𝗙𝗶𝗿𝘀𝘁 𝗗𝗮𝘁𝗲𝘀 𝘇𝗲𝗴𝘁 𝗯𝗮𝗿𝗺𝗮𝗻 𝗩𝗶𝗰𝘁𝗼𝗿 𝘃𝗮𝗮𝗿𝘄𝗲𝗹 𝗺𝗲𝘁 𝘀𝗽𝗲𝗰𝗶𝗮𝗹𝗲 𝘂𝗶𝘁𝘇𝗲𝗻𝗱𝗶𝗻𝗴

Barman Victor Abeln is op 25 maart voor het laatst te zien in datingprogramma First Dates. In deze laatste aflevering met Victor "blikken we terug met een compilatie en bedanken we Victor voor zijn bijdrage". Dat maakte BNNVARA donderdag bekend.

https://www.rtl.nl/boulevard/artikel/5500229/first-dates-zegt-barman-victor-vaarwel-met-speciale-uitzending

#FirstDates #barman #Victor

RDV cet aprem à l'Antre Jeux à #Limoges

🤔💡 PROTOTYPES 💡🤔
C'est après demain, et comme tous les mois des auteurs et autrices du coin viennent faire découvrir leurs prototypes de jeux !
Venez essayer et leur filer le coup de main dont ils ont besoin !
#limogesmaville💖 #instalimoges #antrejeux #friendship #sortiràlimoges #barman #newslimoges #cocktails #cafeludique #jeuxdesociété #fun #barajeux #bières #boardgamecafe #limogestourisme #limogesmaville

https://www.facebook.com/antrejeux

RDV cet aprem à l'Antre Jeux à #Limoges

🤔💡 PROTOTYPES 💡🤔
C'est après demain, et comme tous les mois des auteurs et autrices du coin viennent faire découvrir leurs prototypes de jeux !
Venez essayer et leur filer le coup de main dont ils ont besoin !
#limogesmaville💖 #instalimoges #antrejeux #friendship #sortiràlimoges #barman #newslimoges #cocktails #cafeludique #jeuxdesociété #fun #barajeux #bières #boardgamecafe #limogestourisme #limogesmaville

https://www.facebook.com/antrejeux

𝗕𝗮𝗿𝗺𝗮𝗻 𝗲𝗻 𝗸𝗹𝗮𝗻𝘁 𝘀𝗹𝗶𝗲𝗽𝗲𝗻 𝗶𝗻 𝗸𝗲𝗹𝗱𝗲𝗿 𝗰𝗮𝗳é 𝗧𝗮𝗿𝘄𝗲𝗸𝗮𝗺𝗽: '𝗢𝗻𝗴𝗲𝗹𝗼𝗼𝗳𝗹𝗶𝗷𝗸 𝗱𝗮𝘁 𝘇𝗲 𝗻𝗼𝗴 𝗹𝗲𝘃𝗲𝗻, 𝘃𝗮𝗻 𝗱𝗲 𝗯𝗮𝗿 𝗶𝘀 𝗻𝗶𝗲𝘁𝘀 𝗼𝘃𝗲𝗿'

De barman en een vaste klant van Café Bar Rosa, die zaterdagochtend gewond raakten in Den Haag, sliepen ten tijde van de explosies in de kelder van de horecagelegenheid. "Dat ze nog leven en nauwelijks gewond zijn, is...

https://www.rtl.nl/nieuws/binnenland/artikel/5484421/barman-vrouw-sliepen-kelder-kroeg-aan-de-tarwekamp

#Barman #Klant #CaféTarwekamp

'𝗕𝗮𝗿𝗺𝗮𝗻 𝗲𝗻 𝗸𝗹𝗮𝗻𝘁 𝘀𝗹𝗶𝗲𝗽𝗲𝗻 𝗶𝗻 𝗸𝗲𝗹𝗱𝗲𝗿 𝗸𝗿𝗼𝗲𝗴 𝗮𝗮𝗻 𝗱𝗲 𝗧𝗮𝗿𝘄𝗲𝗸𝗮𝗺𝗽'

De barman en een vaste klant van Café Bar Rosa, die zaterdagochtend gewond raakten aan de Tarwekamp in Den Haag, sliepen ten tijde van de explosies in de kelder van de horecagelegenheid. Dat meldt Omroep West.

https://www.rtl.nl/nieuws/binnenland/artikel/5484405/barman-en-klant-sliepen-kelder-kroeg-aan-de-tarwekamp

#Barman #Klant #Kelder

𝗕𝗮𝗿𝗺𝗮𝗻 𝗯𝗲𝘃𝗲𝘀𝘁𝗶𝗴𝘁: '𝗝𝘂𝘀𝘁𝗶𝗻 𝗧𝗶𝗺𝗯𝗲𝗿𝗹𝗮𝗸𝗲 𝗵𝗮𝗱 𝗺𝗮𝗮𝗿 éé𝗻 𝗺𝗮𝗿𝘁𝗶𝗻𝗶 𝗼𝗽'

Justin Timberlake (43) wist vorige week de nieuwskoppen te halen toen hij werd opgepakt voor rijden onder invloed. De bloeddoorlopen ogen op zijn 'mugshot' voorspellen weinig goeds, maar de zanger zelf blijft volhouden dat hij slechts één martini heeft gedronken. Die bewering wordt nu ondersteund...

https://www.rtlnieuws.nl/entertainment/artikel/5457031/barman-justin-timberlake-martini

#Barman #JustinTimberlake #martiniop

Обзор открытых свободных инструментов для создания резервных копий СУБД PostgreSQL

Перефразируя древнюю мудрость: все люди делятся на 10 типов: те, кто не знает, зачем нужны резервные копии, и те, кто делает резервные копии. В данном обзоре я попробую мал-мала расшифровать свою давнюю табличку (внеся в неё некоторое количество изменений): Обзор наиболее популярных средств для создания резервных копий PostgreSQL. Ибо не вижу я ни подобных обзоров в информационном поле, ни грамотного, с технической точки зрения, подхода к выбору инструмента вообще, и для создания резервных копий (РК) СУБД PostgreSQL в тех организациях, куда заносит профессиональная деятельность, в частности. Основной аргумент выбора: знания и умения текущего системного администратора. Доводилось встречаться со сменой инструмента по причине того, что новый администратор баз данных не знал и не умел уже использовавшийся продукт. Причём использовался вполне себе достойный, но... (конкретики не будет, по причинам, например, секретным, увы мне).

https://habr.com/ru/articles/820349/

#postgresql #barman #walg #pg_probackup #pgbackrest #резервное_копирование #администрирование_баз_данных #администрирование_бд

Обзор открытых свободных инструментов для создания резервных копий СУБД PostgreSQL

Перефразируя древнюю мудрость: все люди делятся на 10 типов: те, кто не знает, зачем нужны резервные копии, и те, кто делает резервные копии. В данном обзоре я попробую мал-мала расшифровать свою давнюю табличку (внеся в неё некоторое количество изменений): Обзор наиболее популярных средств для создания резервных копий PostgreSQL. Ибо не вижу я ни подобных обзоров в информационном поле, ни грамотного, с технической точки зрения, подхода к выбору инструмента вообще, и для создания резервных копий (РК) СУБД PostgreSQL в тех организациях, куда заносит профессиональная деятельность, в частности. Основной аргумент выбора: знания и умения текущего системного администратора. Доводилось встречаться со сменой инструмента по причине того, что новый администратор баз данных не знал и не умел уже использовавшийся продукт. Причём использовался вполне себе достойный, но... (конкретики не будет, по причинам, например, секретным, увы мне).

https://habr.com/ru/articles/820349/

#postgresql #barman #walg #pg_probackup #pgbackrest #резервное_копирование #администрирование_баз_данных #администрирование_бд

Обзор открытых свободных инструментов для создания резервных копий СУБД PostgreSQL

Перефразируя древнюю мудрость: все люди делятся на 10 типов: те, кто не знает, зачем нужны резервные копии, и те, кто делает резервные копии. В данном обзоре я попробую мал-мала расшифровать свою давнюю табличку (внеся в неё некоторое количество изменений): Обзор наиболее популярных средств для создания резервных копий PostgreSQL. Ибо не вижу я ни подобных обзоров в информационном поле, ни грамотного, с технической точки зрения, подхода к выбору инструмента вообще, и для создания резервных копий (РК) СУБД PostgreSQL в тех организациях, куда заносит профессиональная деятельность, в частности. Основной аргумент выбора: знания и умения текущего системного администратора. Доводилось встречаться со сменой инструмента по причине того, что новый администратор баз данных не знал и не умел уже использовавшийся продукт. Причём использовался вполне себе достойный, но... (конкретики не будет, по причинам, например, секретным, увы мне).

https://habr.com/ru/articles/820349/

#postgresql #barman #walg #pg_probackup #pgbackrest #резервное_копирование #администрирование_баз_данных #администрирование_бд

𝗕𝗮𝗿𝗺𝗮𝗻 𝗩𝗶𝗰𝘁𝗼𝗿 𝘀𝘁𝗼𝗽𝘁 𝗯𝗶𝗷 𝗙𝗶𝗿𝘀𝘁 𝗗𝗮𝘁𝗲𝘀: '𝗪𝗶𝗲 𝗻𝗲𝗲𝗺𝘁 𝗺𝗶𝗷𝗻 𝘀𝘁𝗿𝗶𝗸𝗷𝗲 𝗼𝘃𝗲𝗿?'

Een domper voor 'First Dates'-fans: na maître Sergio (53), houdt ook barman Victor (40) het voor gezien. De vertrouwde, knappe verschijning legt uit waarom hij (tijdelijk) vertrekt en doet een oproep aan zijn opvolger.

https://www.rtlnieuws.nl/entertainment/artikel/5447901/barman-victor-stopt-first-dates-vervanger

#Barman #Victor #FirstDates

Thanks #barman! You just saved my ass! ;-)

https://pgbarman.org/

#DisasterRecovery #postgresql

@GuidoKostons @Waldo

(1) Toppie, Guido. 👍
Ik las laatst iets over een #café #eigenaar, die wél de moed had om een gast de deur uit te wijzen, toen die zich 'onfatsoenlijk' uitte'. 👍
In 1978 was ik op #sardinië in een kroeg. Een gast wondt zich op, want hij dacht dat wij #tedeski (duitsers) waren, die hem als #gastarbeider het recht hadden ontzegt om een #kroeg te bezoeken. Die #barman was heel #diplomatiek. Hij ging eerst luisteren naar die gast en kwam terug bij ons met de vraag..(2)

The term ‘barista’ was introduced during Mussolini’s campaign against the use of foreign-languages. It was considered a more Italian word to replace the English term ‘tea lady’.

#barista #baristas #barman #tealady #coffee #coffeelover #coffeemaker #italiancoffee #italy #history #mussolini #QI #notQI

The term ‘barista’ was introduced during Mussolini’s campaign against the use of foreign-languages. It was considered a more Italian word to replace the English term ‘tea lady’.

#barista #baristas #barman #tealady #coffee #coffeelover #coffeemaker #italiancoffee #italy #history #mussolini #QI #notQI

The term ‘barista’ was introduced during Mussolini’s campaign against the use of foreign-languages. It was considered a more Italian word to replace the English term ‘tea lady’.

#barista #baristas #barman #tealady #coffee #coffeelover #coffeemaker #italiancoffee #italy #history #mussolini #QI #notQI

The term ‘barista’ was introduced during Mussolini’s campaign against the use of foreign-languages. It was considered a more Italian word to replace the English term ‘tea lady’.

#barista #baristas #barman #tealady #coffee #coffeelover #coffeemaker #italiancoffee #italy #history #mussolini #QI #notQI

The term ‘barista’ was introduced during Mussolini’s campaign against the use of foreign-languages. It was considered a more Italian word to replace the English term ‘tea lady’.

#barista #baristas #barman #tealady #coffee #coffeelover #coffeemaker #italiancoffee #italy #history #mussolini #QI #notQI

Quick-thinking barman branded 'hero' after helping girls with note disguised as receipt - Mirror Online
#Barman
#Creepy
#Harrassment
https://www.mirror.co.uk/news/us-news/quick-thinking-barman-branded-hero-29673805