From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Day, David" <dday(at)redcom(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: attempting to retrieve column names from information schema fails. |
Date: | 2017-12-04 16:08:15 |
Message-ID: | 21131.1512403695@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Day, David" <dday(at)redcom(dot)com> writes:
> I'm looking on some insights on the following problem on retrieving table column names from the information schema ( postgres 9.6.6 FreeBSD 11.1 )
> When my client starts up up. Each thread ( 10 ) run this command.
> select column_name from information_schema.columns where table_name = 'pep_port_log';
> I have encountered two instances of testing Where the server does not respond to that command.
Hm. Next time it happens, look into pg_stat_activity to see if the
backend process is waiting, and if so for what, and what other processes
are waiting. (I'm wondering about undetected deadlocks, for instance.)
If it's running, maybe you could collect some stack traces to try to
narrow down what it's doing. Actually, a stack trace would be useful
if it's waiting, too.
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2017-12-04 16:44:49 | Re: Centos 6.9 and centos 7 |
Previous Message | Nicola Contu | 2017-12-04 15:57:40 | Re: Centos 6.9 and centos 7 |