timely resumes - Search results in mailing lists
Mailing lists >> pgsql-general >> Thread
2025-05-20 12:17:25 | Re: Logical replication, need to reclaim big disk space (Moreno Andreo)
resume replication between tables before putting schema online. This is safe, even if far from being optimized. It's a migration tool, it won't be used forever, just to move customers from their current
Mailing lists >> pgsql-general >> Thread >> Search in thread (2)
2025-05-01 16:08:07 | Re: Pgbackrest : Resumable backup of same type exists (Abdul Sayeed)
time and resources by reusing valid parts of the incomplete backup. If you're concerned or just reviewing logs, you generally *don’t need to take action* unless: - The resume
Mailing lists >> pgsql-general >> Thread
2024-11-24 20:03:58 | Re: Questions on Upgrading PostgreSQL from 15.0 to 15.9 and Setting Up Streaming Replication (Subhash Udata)
resume from the primary to the standby? Looking forward to your clarification. 2) What do you mean by resource-intensive? If it means network bandwidth, then read the pg_basebackup man page
Mailing lists >> pgsql-general >> Thread
2024-10-30 14:39:30 | Re: Random memory related errors on live postgres 14.13 instance on Ubuntu 22.04 LTS (Vijaykumar Jain)
time ? most likely it looks like a h/w issue, we used to see things like this on bare metals .... which only happened occasionally and then frequently till we moved away from that setup. also, does
Mailing lists >> pgsql-general >> Thread
2024-10-29 22:17:37 | Re: Delays between "connection received" and "connection authenticated" because of localhost entries in hba (Vijaykumar Jain)
this for the time being.
--
Thanks,
Vijay
Open to work
Resume - Vijaykumar Jain
Mailing lists >> pgsql-general >> Thread >> Search in thread (2)
2024-10-19 20:04:59 | explain vs auto_explain (Vijaykumar Jain)
fkey: time=46.274 calls=4
*/
--
Thanks,
Vijay
Open to work
Resume - Vijaykumar Jain
Mailing lists >> pgsql-general >> Thread
2024-10-17 00:58:46 | Logical replication disabled, recovery not possible because of 1 large transaction with schema changes? (Koen De Groote)
resume and run into the same issues. Ok, I update the schema and enable again. It runs into an error for the inserts of step 1. These set values for columns dropped in step
Mailing lists >> pgsql-general >> Thread
2024-08-29 16:24:00 | Re: PgBackRest Full backup and N/W reliability (Greg Sabino Mullane)
resume Any suggestions much appreciated Boost your process-max as high as you are able to speed up your backup time
Mailing lists >> pgsql-general >> Thread
2024-06-10 11:39:18 | Question regarding automatically paused streaming replication (Ian van der Linde)
resume() to continue. The log messages around this time all look normal and there were
Mailing lists >> pgsql-general >> Thread
2024-05-23 10:23:00 | Re: Backup failure Postgres (Torsten Förtsch)
time the COPY takes (reset primary_conninfo). You could increase max_standby_streaming_delay. Perhaps you could also wrap the COPY operation in pg_wal_replay_pause() / pg_wal_replay_resume
Mailing lists >> pgsql-general >> Thread
2024-03-28 14:52:52 | [MASSMAIL]pg_rewind after promote (Emond Papegaaij)
resumed from the new primary * the node that needed to be taken out of the cluster (the old primary) is shutdown and rebooted This works fine most of the time
Mailing lists >> pgsql-general >> Thread
2024-03-09 00:06:20 | Re: Help diagnosing replication (copy) error (Jeff Ross)
times we've had replication simply stop and we could never find any reason for that on either publisher or subscriber. The *only* solution that ever worked in these cases was dropping the subscription
Mailing lists >> pgsql-general >> Thread
2023-11-29 20:25:05 | Query runtime differences- trying to understand why. (Dirschel, Steve)
time zone > resume_date) OR (suspend_date IS NULL) OR (resume_date IS NULL))) Buffers
Mailing lists >> pgsql-general >> Thread
2023-02-12 00:42:35 | Queries running forever, because of wrong rowcount estimate (Peter)
Time: 1941.862 ms" We have this data in pg_class and pg_stats: relpages | reltuples ----------+----------- 1 | 3 attname | n_distinct | most_common_vals | most_common_freqs | histogram_bounds | correlation
Mailing lists >> pgsql-general >> Thread
2023-01-30 08:53:30 | Question on Logical Replication (Venkata B Nagothi)
resume from the time when subscription was disabled ? We just wanna make sure transactions do not go missing