2830
English speaking PostgreSQL public chat. This group is for discussions on PostgreSQL-related topics and strives to provide best-effort support as well.
Also figure out where your bloat is and target it accordingly, queries like those in https://github.com/ioguix/pgsql-bloat-estimation/tree/master and https://wiki.postgresql.org/wiki/Show_database_bloat#Query_from_check_postgres
Читать полностью…
Well, you had it coming with vacuum full. Best idea would be to use pg_repack but as @Suman_PHF10073 said that requires keys
Читать полностью…
Pgrepack addin you could use provided tables has primary keys
Читать полностью…
Can you be a bit more specific? Is there something you struggle with?
Читать полностью…
is pgBackRest incremental is more or less like pg_basebackup incremental in version 17?
Читать полностью…
That's because some Oracle book wrote partitioning = 10X fast and people without any business need or natural key to partition also want to partition. I remembered old oracle blog saying if table is >2GB consider partitioning. 😂
Читать полностью…
As you probably know I have a very strong opinion about hash partitioning, even for sharding. The scaling and flexibility is just too limited for me.
Читать полностью…
Strictly speaking: yes. But it would require you to build the hashed table in the background. When you are ready you lock both tables and swap the names.
I would strongly advise to rethink your partitioning set up. When you use hash partitioning you can get a lot of full page writes on your index because of the random inset positions. It is also very hard to expand the number of partitions in the future.
I would recommend range based partitioning. Maybe investigate the uuidv7 data type for your partitioning column.
Looking for Postgre sql DBA support on Monday 2pm -2:45pm CST
Читать полностью…
Looking for Oracle DBA opportunity with 9.5+ years of experience.... Please let me know if any openings
Читать полностью…
There's also --clone now, for some filesystems. Combines the best of both worlds.
Since the postgresql on-disk format is mostly static, most files will just be hardlinked
Читать полностью…
The safest is using copy, it'll also as a bonus check if all the files are okay and refresh bitrot on ZFS pools / RAID arrays 😺
Читать полностью…
It would be good to understand why you need a vacuum full given that a database in good health should do just fine with autovacuum
Читать полностью…
Is it actually the tables that are bloated or the indexes? If the latter consider also the native REINDEX...CONCURRENTLY?
Читать полностью…
I will now elaborate on my current activities. We are experiencing a significant downtime of approximately 8 hours for a full vacuum during database maintenance, given that some of our databases are around 1TB in size. This extended downtime is a considerable concern. Do you have any recommendations for reducing or eliminating this downtime?
Читать полностью…
Hi Team, I’d like to understand best practices for PostgreSQL database maintenance on a live production instance with zero or minimal downtime.
Читать полностью…
It is similar in its effect, but the implementation is quite different. pgBackRest is based on checksums (so it still has to read a lot on the server) while the builtin incremental method relies on a logfile tracking all changed pages.
Also, pgbackrest can't combine old backups to create new full backups, AFAIK.
Seems like it is very popular in the Oracle realm. One wonders why... Probably a good source for consulting hours...
Читать полностью…
Is there any serious use case for hash partitioning apart from sharding? 🤔
Читать полностью…
is this possible to convert a big table into hash partitioned on-line?
Читать полностью…
It's not received the hype coverage it deserves... also, the list of filesystems actually supporting it is rather short.
And the rsync trick for replicas doesn't work with it AFAICS, so it's not for everyone.
link means it will create the new upgraded version with hardlinks to the old datafiles? so it will modify the older version?
copy is the safest but it takes longer to copy the hole data?
I use --link because my filesystem supports snapshots, so i can go back to the old snapshots and undo the upgrade if anything happens. But if something bad happens, the files that were changed by the newer postgresql version during the upgrade will not work on the older one.
Читать полностью…