[pgpool-general: 1136] Re: pgpool segfault (getting nowhere)

[Tatsuo Ishii]

I have took a look at the backtrace and found the #0 starck trace is
strange. It seems pool_add_query_cache_array() totaly different from
its actual function signature.

pool_add_query_cache_array(POOL_QUERY_CACHE_ARRAY *cache_array, POOL_TEMP_QUERY_CACHE *cache)

The number of parameters of pool_add_query_cache_array is 2, while the
stack trace thinks 4.

Anyway, pool_memqcache.c:2529 is this:

	cache_array->caches[cache_array->num_caches++] = cache;

Can you print the value of variables?

cache_array
cache_array->caches
cache_array->num_caches

#0  0x000000000044c16a in pool_add_query_cache_array (backend=0xdfe1e60, query=0xe00e5f8 "SELECT *\nFROM dms.dm_doc_category\nWHERE \"parent_id\" = '244'\nORDER BY label asc", node=<value optimized out>, state=84 'T')
    at pool_memqcache.c:2529
#1  pool_handle_query_cache (backend=0xdfe1e60, query=0xe00e5f8 "SELECT *\nFROM dms.dm_doc_category\nWHERE \"parent_id\" = '244'\nORDER BY label asc", node=<value optimized out>, state=84 'T') at pool_memqcache.c:2937
#2  0x0000000000446af5 in ReadyForQuery (frontend=0xe005100, backend=0xdfe1e60, send_ready=1 '\001', cache_commit=1 '\001') at pool_proto_modules.c:1760
#3  0x0000000000446f4a in ProcessBackendResponse (frontend=0xe005100, backend=0xdfe1e60, state=0x7fff14597d00, num_fields=0x7fff14597d04) at pool_proto_modules.c:2590
#4  0x000000000041a3b5 in pool_process_query (frontend=0xe005100, backend=0xdfe1e60, reset_request=0) at pool_process_query.c:274
#5  0x000000000040a378 in do_child (unix_fd=5, inet_fd=6) at child.c:362
#6  0x00000000004046e5 in fork_a_child (unix_fd=5, inet_fd=6, id=51) at main.c:1243
#7  0x0000000000407184 in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:661

> hi all,
> 
> I have been having problem with pgpool in my development environment. I
> have reported here :
> 
> http://www.pgpool.net/mantisbt/view.php?id=28
> 
> has anyone facing similar issue ? I appreciate if you share.