[pgpool-hackers: 4234] Re: segmentation fault error
稲垣毅 / INAGAKI,TSUYOSHI
tsuyoshi.inagaki.ej at hitachi.com
Thu Dec 1 11:29:55 JST 2022
Hi, Ishii-san.
Sorry for the late reply, I was organizing the information.
>case T_InsertStmt:
>
>which is absolutely nonsense because the stack #1 is processing T_List. There's no such a thing in a parse tree which consists of list of INSERT statements.
>From which information is the jump destination T_InsertStmt?
#3 on the stack is inside case T_SelectStmt:, so it is recognized as a SELECT statement.
Also, I could be confirmed that the SQL I was executing was a SELECT statement.
>Can you share pgpool.conf and pgpool log?
I'll pick it up and send it to you.
Please let me know if you need any additional information.
pgpool log
[2022-11-08 00:09:29][14402][main] WARNING: child process with pid: 24266 was terminated by segmentation fault
[2022-11-08 00:09:29][14402][main] LOG: fork a new child process with pid: 10357
The previous log for pid:24266 is below.(It's old, so I don't think it will affect it.)
[2022-11-07 21:00:02][24266][psql] LOG: pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 17873 statement: xxx
pgpool.conf
I'll let you know what the parameters change.
--
listen_addresses = '*'
backend_hostname0 = 'db01'
backend_port0 = 5432
backend_weight0 = 1
backend_data_directory0 = '/data'
backend_flag0 = 'ALLOW_TO_FAILOVER'
backend_application_name0 = 'db01'
backend_hostname1 = 'db02'
backend_port1 = 5432
backend_weight1 = 1
backend_data_directory1 = '/data'
backend_flag1 = 'ALLOW_TO_FAILOVER'
backend_application_name1 = 'db02'
enable_pool_hba = on
pool_passwd = 'pool_passwd'
num_init_children = 1100
max_pool = 1
child_life_time = 0
connection_life_time = 30s
client_idle_limit = 7200s
log_line_prefix = '[%t][%p][%a] '
log_hostname = on
log_rotation_size = 2097151
sr_check_period = 30
delay_threshold = 10000000
follow_primary_command = '/etc/pgpool-II/follow_primary.sh %d %h %p %D %m %H %M %P %r %R'
health_check_period = 3
health_check_timeout = 3
health_check_user = 'postgres'
health_check_max_retries = 2
health_check_retry_delay = 1
health_check_period0 = 3
health_check_timeout0 = 3
health_check_user0 = 'postgres'
health_check_max_retries0 = 2
health_check_retry_delay0 = 1
connect_timeout0 = 10000
health_check_period1 = 3
health_check_timeout1 = 3
health_check_user1 = 'postgres'
health_check_max_retries1 = 2
health_check_retry_delay1 = 1
connect_timeout1 = 10000
failover_command = '/etc/pgpool-II/failover.sh %d %h %p %D %m %H %M %P %r %R %N %S'
failover_on_backend_error = off
search_primary_node_timeout = 60
use_watchdog = on
hostname0 = 'pg01'
wd_port0 = 9000
pgpool_port0 = 9999
hostname1 = 'pg02'
wd_port1 = 9000
pgpool_port1 = 9999
hostname2 = 'pg03'
wd_port2 = 9000
pgpool_port2 = 9999
delegate_IP = '192.168.0.101'
wd_escalation_command = '/etc/pgpool-II/escalation.sh'
wd_de_escalation_command = '/etc/pgpool-II/de-escalation.sh'
enable_consensus_with_half_votes = on
wd_lifecheck_method = 'heartbeat'
wd_interval = 3
heartbeat_hostname0 = 'pg01'
heartbeat_port0 = 9694
heartbeat_hostname1 = 'pg02'
heartbeat_port1 = 9694
heartbeat_hostname2 = 'pg03'
heartbeat_port2 = 9694
wd_heartbeat_deadtime = 10
relcache_expire = 3600
--
Regards,
--
Tsuyoshi Inagaki
tsuyoshi.inagaki.ej �� hitachi.com
More information about the pgpool-hackers
mailing list