Vaccum locking tables (Recipient)

Avatar

Avatar
Validate 1
Level 4
pierrec70731455
Level 4

Likes

62 likes

Total Posts

59 posts

Correct reply

14 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 25
View profile

Avatar
Validate 1
Level 4
pierrec70731455
Level 4

Likes

62 likes

Total Posts

59 posts

Correct reply

14 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 25
View profile
pierrec70731455
Level 4

22-05-2019

Hi,

The Vaccuum process runs on a regular basis and we notice it sometimes blocks Update Data on tables such as Recipient and even an Enrichment activity on Recipient which is basically a select.

The Neolane Support told us :

Does anybody have any suggestion regarding this?

Can it really not be excluded during some time slots like the office hours?

Kind regards,

Pierre

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Establish
MVP
wodnicki
MVP

Likes

986 likes

Total Posts

1,097 posts

Correct reply

518 solutions
Top badges earned
Establish
Affirm 500
Contributor
Shape 1
Give Back 100
View profile

Avatar
Establish
MVP
wodnicki
MVP

Likes

986 likes

Total Posts

1,097 posts

Correct reply

518 solutions
Top badges earned
Establish
Affirm 500
Contributor
Shape 1
Give Back 100
View profile
wodnicki
MVP

22-05-2019

Hi,

Autovacuum? That doesn't lock tables, and afaik nothing locks read access outside alter table, truncate, vacuum full.

Could just be an undersized db struggling with any load, I see them all the time.

Thanks,

-Jon

Answers (1)

Answers (1)

Avatar

Avatar
Validate 1
Level 4
pierrec70731455
Level 4

Likes

62 likes

Total Posts

59 posts

Correct reply

14 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 25
View profile

Avatar
Validate 1
Level 4
pierrec70731455
Level 4

Likes

62 likes

Total Posts

59 posts

Correct reply

14 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 25
View profile
pierrec70731455
Level 4

29-05-2019

Hi,

it indeed wasn't the autovaccum causing the issue.

Kind regards,

Pierre