Re: nested hstore patch - FailedAssertion("!(value->array.nelems == 1)

Поиск
Список
Период
Сортировка
От Erik Rijkers
Тема Re: nested hstore patch - FailedAssertion("!(value->array.nelems == 1)
Дата
Msg-id d20ce0f33bf56d61f05f2ede5a4cc932.squirrel@webmail.xs4all.nl
обсуждение исходный текст
Ответ на Re: nested hstore patch - FailedAssertion("!(value->array.nelems == 1)  (Oleg Bartunov <obartunov@gmail.com>)
Ответы Re: nested hstore patch - FailedAssertion("!(value->array.nelems == 1)  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-hackers
On Wed, January 15, 2014 09:46, Oleg Bartunov wrote:
>> On Wed, January 15, 2014 08:01, Oleg Bartunov wrote:
>>> It doesn't crashed in the last version in our repository.
>>>
>>> =# select  'x'::hstore || ('a=>"1"':: hstore) ;
>>>    ?column?
>>> ---------------
>>>  "x", "a", "1"
>>> (1 row)
>>>
>>
>> OK, shall I use that repository instead of the latest posted patch?

I now installed from: https://github.com/feodor/postgres

and compiled both a 'fast' and a 'debug' server (=with --enable-cassert see [1])

It turns out that the statement does not crash on a server compiled without --enable-cassert.

But a compile with --enable-cassert shows that a bug is still lurking:

testdb=# select  'x'::hstore || ('a=>"1"':: hstore) ;
The connection to the server was lost. Attempting reset: Failed.
!>

TRAP: FailedAssertion("!(value->array.nelems == 1)", File: "hstore_support.c", Line: 896)


Not good.


( please note that the assert is in a different file ('hstore_support.c') from the earlier assert error that I posted
)


Thanks,

Erik Rijkers




[1]
pg_config:
'--prefix=/home/aardvark/pg_stuff/pg_installations/pgsql.nested_hstore_url'
'--bindir=/home/aardvark/pg_stuff/pg_installations/pgsql.nested_hstore_url/bin'
'--libdir=/home/aardvark/pg_stuff/pg_installations/pgsql.nested_hstore_url/lib' '--with-pgport=46541'
'--enable-depend'
'--enable-cassert' '--enable-debug' '--with-openssl' '--with-perl' '--with-libxml' '--with-libxslt' '--with-zlib'






В списке pgsql-hackers по дате отправления:

Предыдущее
От: Ashutosh Bapat
Дата:
Сообщение: Re: identify table oid for an AggState during plan tree initialization
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: plpgsql.warn_shadow