本文介绍了时间范围扩展 - 无法访问max_locks_per_transaction参数的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用带有Azure数据库的PostSSQL的TimeScale扩展。


执行查询时出错"共享内存提示"提示:您可能需要增加max_locks_per_transaction" 。


max_locks_per_transaction在服务器参数中不可用,我无法按照锁定设置的时间刻度的要求设置服务器:  https://docs.timescale.com/v1.3/getting-started/configuring#locks


顺便说一下,TimeScale扩展并不适用于Azure数据库for PostgreSQL。


有任何想法或建议来设置此参数并使TimeScale服务器正常运行并正常运行吗? 


非常感谢您的支持

解决方案


I am using TimeScale extension with Azure Database for PostgreSQL.

I have an error while executing queries "out of shared memory Hint: You might need to increase max_locks_per_transaction".

The max_locks_per_transaction is not available in server parameters and I cannot setup the server as requested by timescale for lock settings :  https://docs.timescale.com/v1.3/getting-started/configuring#locks

By the way, TimeScale extension is not really usable with Azure Database for PostgreSQL.

Any idea or suggestion to set this parameter and to get a TimeScale server up&running properly ? 

Thanks a lot for your support

解决方案


这篇关于时间范围扩展 - 无法访问max_locks_per_transaction参数的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-25 05:26