Re: Segmentation fault in case Debian9+odbc+pgsql10.6
От | Yuriy Nasida |
---|---|
Тема | Re: Segmentation fault in case Debian9+odbc+pgsql10.6 |
Дата | |
Msg-id | CADihe3+83tvMrNYrVBUqiZtuvFDTXzmyhm1zpF7XWs8AT94+MA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Segmentation fault in case Debian9+odbc+pgsql10.6 ("Inoue, Hiroshi" <h-inoue@dream.email.ne.jp>) |
Ответы |
Re: Segmentation fault in case Debian9+odbc+pgsql10.6
("Inoue, Hiroshi" <h-inoue@dream.email.ne.jp>)
|
Список | pgsql-odbc |
Thanks Hiroshi,
I tried to comment these settings in postgresql.conf and even sent it defferently. Nothing helps.
Btw, I have pgsql 10.6 (Centos 7) and latest version of odbc-postgresql 1:09.05.0400-2 at (Debian9)
That is why bug you mentioned should be already fixed with my setup.
But you have lead me to other idea. My postgresql.conf files is copy-pasted from my pgsql9.2. May be some setting was changes and it's te reason of segfault? But like I said all worked fine when I tested with Deb8 which had old version of odbc-postgresql.
Please advice.
On Wed, 28 Nov 2018 at 08:28, Inoue, Hiroshi <h-inoue@dream.email.ne.jp> wrote:
Hi Yuriy,
The crash seems to be caused by setting log_min_duration_statement = 0 or log_duration = on
in postgresql.conf. The bug was fixed in 9.06.0100. Please avoid the setting in postgresql.conf
or upgrade the driver.
regards,
Hiroshi InoueOn 2018/11/27 1:01, Yuriy Nasida wrote:Hi guys,FYI - I noted that i have not problems with Deb9+pgsql9 and with Deb8+pgsql10But! I get segmentation fault in case Debian9+odbc+pgsql10.6Did you get something like this ?Please look at some info below.My odbc.ini:[pgsqldsn]Driver = /usr/lib/x86_64-linux-gnu/odbc/psqlodbcw.soSetup = /usr/lib/x86_64-linux-gnu/odbc/libodbcpsqlS.soDatabase=dbnameServername=ipPort=5432Username=rootPassword=superpasswdDebug=0CommLog=1UsageCount=1RowVersioning=NoShowSystemTables=NoShowOidColumn=NoFakeOidIndex=NoConnSettings=odbc version:odbc-postgresql:amd64 1:09.05.0400-2# isql -v pgsqldsnDEBUG: CommitTransaction(1) name: unnamed; blockState: STARTED; state: INPROGR, xid/subid/cid: 0/1/0Segmentation faultPgsql logs:DEBUG: forked new backend, pid=36868 socket=11DEBUG: postmaster child[36868]: starting with (DEBUG: postgresDEBUG: )DEBUG: InitPostgresDEBUG: my backend ID is 5DEBUG: StartTransaction(1) name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0DEBUG: received password packetDEBUG: CommitTransaction(1) name: unnamed; blockState: STARTED; state: INPROGR, xid/subid/cid: 0/1/0DEBUG: StartTransaction(1) name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0STATEMENT: SET DateStyle = 'ISO'DEBUG: CommitTransaction(1) name: unnamed; blockState: STARTED; state: INPROGR, xid/subid/cid: 0/1/0STATEMENT: SET DateStyle = 'ISO'LOG: duration: 0.271 ms statement: SET DateStyle = 'ISO'DEBUG: StartTransaction(1) name: unnamed; blockState: DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0STATEMENT: SET extra_float_digits = 2DEBUG: CommitTransaction(1) name: unnamed; blockState: STARTED; state: INPROGR, xid/subid/cid: 0/1/0STATEMENT: SET extra_float_digits = 2LOG: duration: 0.171 ms statement: SET extra_float_digits = 2DEBUG: unexpected EOF on client connectionDEBUG: shmem_exit(0): 1 before_shmem_exit callbacks to makeDEBUG: shmem_exit(0): 6 on_shmem_exit callbacks to makeDEBUG: proc_exit(0): 3 callbacks to makeDEBUG: exit(0)DEBUG: shmem_exit(-1): 0 before_shmem_exit callbacks to makeDEBUG: shmem_exit(-1): 0 on_shmem_exit callbacks to makeDEBUG: proc_exit(-1): 0 callbacks to makeDEBUG: reaping dead processesDEBUG: server process (PID 36868) exited with exit code 0Any advice ?Thanks.
В списке pgsql-odbc по дате отправления:
Предыдущее
От: "Inoue, Hiroshi"Дата:
Сообщение: Re: Segmentation fault in case Debian9+odbc+pgsql10.6
Следующее
От: "Inoue, Hiroshi"Дата:
Сообщение: Re: Segmentation fault in case Debian9+odbc+pgsql10.6