Nothing to do from pgbackrest side, you should look at what's writing that much Wal and optimise. Compression type zstd or lz4 works best but not going to help with rate of growth.
Читать полностью…Hey guys,
I use pgbackrest as my backup tool. However, I noticed that my repository keep on growing so quickly and largely.
Is there any way to optimise this pls? anything to do other than decide on archive_timeout parameter or compressing?
What is the best way to use a long running query in standby node? It has streaming configured. Looks vacuum issue occur when Hot_standby_feedback=on
Читать полностью…Probably aurora is the issue. Does it have access (is anything else connecting using same fdw) or does it kill/block that session? Did you check security groups settings in aurora?
Читать полностью…hello, just install pg17 cluster, and try to get cluster info from bgw_replstatus, but pg throws
ERROR: could not find function "bgw_replstatus_main" in file "/usr/pgsql-17/lib/bgw_replstatus.so"
is there bug or something I miss
Wait event message is clear. You need to debug on Aurora. They have performamce insight, explain plan and AWS support.
Читать полностью…Well, pg_stat_activity from AWS, wireshark locally.
You may want to log ssl keys if you use ssl (something like https://github.com/wpbrown/openssl-keylog ), however even without that keys wireshark gathers some reasonable info.
Also, it could be connection/mtu issues. Wireshark also could help, but just disabling path mtu discovery and using minimal packets — could solve this problem.
Anyone have idea about data engineers and skills required for same or the tools which are helpful?? Kindly share me the path!! DM me..
Читать полностью…Hello and welcome to this chat. Here we discuss PostgreSQL and provide best-effort voluntary support on Postgresql issues.
If you have any question, try asking kindly, including log files, error descriptions and perhaps what you're trying to do.
- 🚫 photos and screenshots
- 🚫 spam and offtopic
- ✅ questions with log files and clear explanation of what's gone wrong
⬇️ Press the button down here ⬇️
What's your retention policy? Are you concerned with total size or just rate of growth?
Читать полностью…There is no perfect solution. You might consider using a logical replica instead of a binary replica for very long-running queries.
Читать полностью…okay. I tried to see the session running on the aurora side and I could not see the session related to my query there.
Is there something that the query has even crossed my Server(FWD extension could be the issue)?
AFAIK the last release broke some ABIs, which is why there was an intermediate release end of November. Are you on 17.2?
Also, did you set
shared_preload_libraries = 'bgw_replstatus'
Well, apart from hundreds of snake oil products that you can probably buy for the purpose, there's e.g. https://www.gpg4win.org/
Читать полностью…Hi
I have PostgreSQL db on prem and I am running a query which includes few foreign tables sit on AWS aurora PostgreSQL read only instance.
This query stuck for ever with wait event "External" anad event type "External"
Other query which is having foreign tables are running and giving output .
Any thoughts? Any suggestions how to debug it?
thank u for your response about
https://gist.github.com/rogergcc/913dee43310d35cda9a3383e094bed1b#file-aqp-geojson
Pgbackrest has encryption built in. If you use a repo host on top, you can divide your eggs into different baskets, which is a Good Thing (TM)
Читать полностью…Honestly, this gets complicated... Whatever monitoring tool you use, you should point at these things. And set appropriate alarms. I've written my own, as well as leveraged a few others. A couple free Nagios, etc. As well as paid ones.
The important things are:
1) Monitoring
2) At least DUMPING (pg_dump), and practicing your restores
3) Having Backups, and testing the restores. PgBackrest, etc. etc.
Without that. You are BEGGING for data loss. (My personal NAS just died b/c the power supply).
Stuff Happens. And you are not a professional if you don't know how to recover your DB! LOL