And please be sure that default permissions are defined properly. Otherwise it
may happen that userA creates a new table but userB has access for that.
Alternative option is that user has to grant proper access for the role group
after every time when a new db object is created.
Toomas
> On 1
Hi,
Basically I had the same topic recently and based on observation I would say
that configuration parameter hot_standby_feedback disables no only some
vacuuming operations but something else as well. I played thru the same
scenario where I disabled hot_standby_feedback and and vacuuming, but
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
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
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
identify where is the conflict that stops replication and forces to
terminate a query on standby host?
BR,
Toomas
> On 17. Jun 2020, at 16:38, Toomas Kristin wrote:
>
> Hi Laurenz,
>
> Thank you!
>
> What are reasons for conflicts? Based on documentation seems that the
-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
Hi!
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 changes for vacuuming on master nor max_standby_
Hi,
Basically seems that data science and machine learning are going to be more and
more popular at every field of life. I have considered to use machine learning
top of logs generated by PostgreSQL servers. However before I start maybe
someone already has done that and can share some experienc
