On Sat, 2020-06-20 at 06:51 +0300, Toomas Kristin wrote:
> Thank you for help. hot_standby_feedback did what I expected (no lag on
> replication
> and no session termination) and case is closed. Only it is foggy for me how
> it can
> be when no logs about vacuuming from that time window when sess
Hi Laurenz,
> Yes, that are conflicts with VACUUM.
Thank you for help. hot_standby_feedback did what I expected (no lag on
replication and no session termination) and case is closed. Only it is foggy
for me how it can be when no logs about vacuuming from that time window when
session is active
On Fri, 2020-06-19 at 11:46 +0300, Toomas Kristin wrote:
> I executed a database dump with 4 jobs and here are logs how this ended.
>
> 2020-06-19 02:38:28 UTC:[30953]:ERROR:40001:canceling statement due to
> conflict with recovery
> 2020-06-19 02:38:28 UTC:[30953]:DETAIL:User query might have ne
Hi,
Thank you all for help.
> FWIW in case you haven't tried yet, if you could find a DETAILS: line
> following to the ERROR: canceling.." message in server log, it would
> narrow the possibility.
I executed a database dump with 4 jobs and here are logs how this ended.
2020-06-19 02:38:28 UTC
At Thu, 18 Jun 2020 23:29:49 +0300, Toomas Kristin
wrote in
> Hi,
>
> > There can be other reasons:
> >
> > - replicated ACCESS EXCLUSIVE locks that conflict with queries
> > - replicated ACCESS EXCLUSIVE locks that cause deadlocks
> > - buffer pins that are needed for replication but held by
Hi,
> There can be other reasons:
>
> - replicated ACCESS EXCLUSIVE locks that conflict with queries
> - replicated ACCESS EXCLUSIVE locks that cause deadlocks
> - buffer pins that are needed for replication but held by a query
> - dropped tablespaces that hold temporary files on the standby
Tha
On Thu, 2020-06-18 at 10:09 +0300, Toomas Kristin wrote:
> What is difference between following error messages?
>
> ERROR: canceling statement due to conflict with recovery
> FATAL: terminating connection due to conflict with recovery
One kills your database session, the other doesn't.
> I tri
Toomas Kristin wrote:
> > > Basically after upgrade to version 11.5 from 10.6 I experience error
> > > messages on streaming
> > > replica host “FATAL: terminating connection due to conflict with
> > > recovery” and
> > > “ERROR: canceling statement due to conflict with recovery”. There is no
>
Hi!
What is difference between following error messages?
ERROR: canceling statement due to conflict with recovery
FATAL: terminating connection due to conflict with recovery
I tried to correlate process termination on standby and vacuuming on master.
Here is a sample timeline
1) 2020-06-17 22
Hi Laurenz,
Thank you!
What are reasons for conflicts? Based on documentation seems that the only
reason can be that vacuum removed unused tuples that are in use at standby host
and due to that standby host cannot apply modifications while blocking query
either finishes or will be terminated.
On Wed, 2020-06-17 at 08:42 +0300, Toomas Kristin wrote:
> Basically after upgrade to version 11.5 from 10.6 I experience error messages
> on streaming
> replica host “FATAL: terminating connection due to conflict with recovery”
> and
> “ERROR: canceling statement due to conflict with recovery”.
11 matches
Mail list logo
