On Sat, Nov 2, 2019 at 8:52 PM Konstantin Gredeskoul
wrote:
> A related question is — *how can you avoid doing auto vacuum during the
> busy peak hours, and do more aggressive auto vacuuming at night during low
> traffic?* Is that possible?
>
> I tried achieving that with a manual vacuum, but tha
I have a follow up question on *hot_standby_feedback*.
If I have 3 read replicas that all have this set to ON, and someone runs a
very long query on *one* of the replicas, can all three replicas fall
behind until the query is finished? This is the behavior I observed more
than once, but I can’t se
Thanks Yes it is in c++. Actually we just written this code.
Due to vaccum full cursor query failing on a connection and all the subsequent
queries are failing and we
found shared errors in /var/logs of the postgres installed machine.
We also last query sent by the client application is:
replic
Jason Ralph writes:
> I am trying to find out if the naming convention from autovacuum does what
> its command line equivalent does, or at least what I think it does.
> QUERY: autovacuum: VACUUM ANALYZE table versus autovacuum: VACUUM ANALYZE
> table.
> I have been getting my autovacuum tuned
On 11/1/19 7:49 PM, Jason Ralph wrote:
Hello list,
I am trying to find out if the naming convention from autovacuum does what its
command line equivalent does, or at least what I think it does.
QUERY: autovacuum: VACUUM ANALYZE table versus autovacuum: VACUUM ANALYZE table.
The above are the
