K
K
Kirill Ponomarev2018-03-09 20:29:01
PostgreSQL
Kirill Ponomarev, 2018-03-09 20:29:01

Why is the DBMS error thrown?

Good time. I can not understand why the error 1C falls out. Bundle 1C+Postgresql+Ubuntu. And the speed of work is not encouraging, although only the hardware has been updated.
I apologize for the terrible quality, they sent me a photo.
5aa29eba67da7272896618.jpeg
Maybe someone knows what gives such problems? Postgresql settings? Conf 1C?
postgresql.conf:

shared_buffers = 4GB
temp_buffers = 256MB
work_mem = 128MB
maintenance_work_mem = 1024MB
dynamic_shared_memory_type =
posix max_wal_size = 4GB
min_wal_size = 2GB
checkpoint_completion_target = 0.9
wal_buffers = -1
effective_cache_size = 12GB
autovacuum = on
autovacuum_snaptime =

Answer the question

In order to leave comments, you need to log in

2 answer(s)
B
betonaKilometer, 2018-03-10
@betonaKilometer

You can understand step by step. Firstly, you need to make sure that it’s not just postgresql, postgresql 1C
https://postgrespro.ru/products/1c_build - rearrange if necessary, the second is to create an empty new 1C database - go into it with the configurator and the enterprise - will there be an error, respectively, if no - then questions to the 1C database to the data set. If there is no error - download the Gilev test www.gilev.ru/tpc1cgilv if there is no error again - even more suspicion of the database. Regarding the performance of postgree and 1C - Win and MSSQL are faster on average in the hospital - the platform makes not very optimal queries. www.gilev.ru/category/postgresql-2
Judging by the config - after fixing the error, you need to optimize the config based on the hardware parameters and looking at the Gilev test. By default, it is for small databases on weak machines - to run anywhere after installation.

D
Dmitry Kinash, 2018-03-10
@Dementor

If you have version 8.2, then this is a platform error - you need to upgrade.
Otherwise, you need to do a VACUUM FULL VERBOSE for the pg_catalog table, and if there are error messages, then you also need to reindex it. If the errors continue, then you will need to configure registration in the technological event log EXCP and DBPOSTGRS (Postgresql queries), and then send this data to the support service.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question