On 2024-May-23, Jethish Jethish wrote:
> I have tried by increasing the max_standby_streaming_delay but I'm facing
> lag issues on the replica server.
>
> When i increase the max_standby_streaming_delay even if a query runs for 2
> minutes I'm facing lag issues for 2 minutes.
You could use a sep
Look, you have to compromise somewhere. Let me explain the problem. PG uses
MVCC. That means if you update or delete rows, rows are not actually
modified or added back to free space. They are just marked for later
removal. That actual removal is VACUUM's task. The reason for doing so is
that a conc
Hi Torsten,
I have tried by increasing the max_standby_streaming_delay but I'm facing
lag issues on the replica server.
When i increase the max_standby_streaming_delay even if a query runs for 2
minutes I'm facing lag issues for 2 minutes.
Please suggest here.
Data size is 3TB
On Thu, May 23, 2
As the error message says, your query was aborted due to it conflicting
with recovery. There are many ways to deal with that. You could enable
hot_standby_feedback on the replica. You could disconnect the replica from
the master for the time the COPY takes (reset primary_conninfo). You could
increa
I'm frequently facing the below error while performing backup. Someone
please tell how solve this issues.
Failed : pg_dump: error: Dumping the contents of table "botsession" failed:
PQgetResult() failed. pg_dump: error: Error message from server: ERROR:
canceling statement due to conflict with re
