Re: Segmentation fault in case Debian9+odbc+pgsql10.6

Hi Yuriy,

Could you please try to set client_min_messages to default(notice)?

regards,
Hiroshi Inoue

On 2018/11/28 17:02, Yuriy Nasida wrote:
> 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(at)dream(dot)email(dot)ne(dot)jp <mailto:h-inoue(at)dream(dot)email(dot)ne(dot)jp>> wrote:
>
> Hi Yuriy,
>
> The crash seems to be caused by setting log_min_duration_statement
> = 0 orlog_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 Inoue
>
> On 2018/11/27 1:01, Yuriy Nasida wrote:
>> Hi guys,
>>
>> FYI - I noted that i have not problems with Deb9+pgsql9 and with
>> Deb8+pgsql10
>> But! I get *segmentation fault* in case *Debian9+odbc+pgsql10.6*
>>
>> Did you get something like this ?
>>
>> Please look at some info below.
>>
>> My *odbc.ini:*
>>
>> [pgsqldsn]
>> Driver = /usr/lib/x86_64-linux-gnu/odbc/psqlodbcw.so
>> Setup = /usr/lib/x86_64-linux-gnu/odbc/libodbcpsqlS.so
>> Database=dbname
>> Servername=ip
>> Port=5432
>> Username=root
>> Password=superpasswd
>> Debug=0
>> CommLog=1
>> UsageCount=1
>> RowVersioning=No
>> ShowSystemTables=No
>> ShowOidColumn=No
>> FakeOidIndex=No
>> ConnSettings=
>>
>> odbc version:
>> *odbc-postgresql:amd64             1:09.05.0400-2*
>>
>> # isql -v pgsqldsn
>> DEBUG:  CommitTransaction(1) name: unnamed; blockState: STARTED;
>> state: INPROGR, xid/subid/cid: 0/1/0
>> *Segmentation fault*
>> *
>> *
>> Pgsql logs:
>>
>> DEBUG:  forked new backend, pid=36868 socket=11
>> DEBUG:  postmaster child[36868]: starting with (
>> DEBUG: postgres
>> DEBUG:  )
>> DEBUG:  InitPostgres
>> DEBUG:  my backend ID is 5
>> DEBUG:  StartTransaction(1) name: unnamed; blockState: DEFAULT;
>> state: INPROGR, xid/subid/cid: 0/1/0
>> DEBUG:  received password packet
>> DEBUG:  CommitTransaction(1) name: unnamed; blockState: STARTED;
>> state: INPROGR, xid/subid/cid: 0/1/0
>> DEBUG:  StartTransaction(1) name: unnamed; blockState: DEFAULT;
>> state: INPROGR, xid/subid/cid: 0/1/0
>> STATEMENT:  SET DateStyle = 'ISO'
>> DEBUG:  CommitTransaction(1) name: unnamed; blockState: STARTED;
>> state: INPROGR, xid/subid/cid: 0/1/0
>> STATEMENT:  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/0
>> STATEMENT:  SET extra_float_digits = 2
>> DEBUG:  CommitTransaction(1) name: unnamed; blockState: STARTED;
>> state: INPROGR, xid/subid/cid: 0/1/0
>> STATEMENT:  SET extra_float_digits = 2
>> LOG:  duration: 0.171 ms  statement: SET extra_float_digits = 2
>> DEBUG:  unexpected EOF on client connection
>> DEBUG:  shmem_exit(0): 1 before_shmem_exit callbacks to make
>> DEBUG:  shmem_exit(0): 6 on_shmem_exit callbacks to make
>> DEBUG:  proc_exit(0): 3 callbacks to make
>> DEBUG:  exit(0)
>> DEBUG:  shmem_exit(-1): 0 before_shmem_exit callbacks to make
>> DEBUG:  shmem_exit(-1): 0 on_shmem_exit callbacks to make
>> DEBUG:  proc_exit(-1): 0 callbacks to make
>> DEBUG:  reaping dead processes
>> DEBUG:  server process (PID 36868) exited with exit code 0
>>
>>
>> Any advice ?
>> Thanks.
>

---
このメールは、AVG によってウイルス チェックされています。
http://www.avg.com