| From: | Satoshi Nagayasu <snaga(at)uptime(dot)jp> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Assert in pg_stat_statements |
| Date: | 2015-08-08 09:00:26 |
| Message-ID: | 55C5C52A.40107@uptime.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I just found that pg_stat_statements causes assert when queryId is
set by other module, which is loaded prior to pg_stat_statements in
the shared_preload_libraries parameter.
Theoretically, queryId in the shared memory could be set by other
module by design.
So, IMHO, pg_stat_statements should not cause assert even if queryId
already has non-zero value --- my module has this problem now.
Is my understanding correct? Any comments?
Regards,
--
NAGAYASU Satoshi <snaga(at)uptime(dot)jp>
| Attachment | Content-Type | Size |
|---|---|---|
| pg_stat_statements.c.diff | text/plain | 862 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shay Rojansky | 2015-08-08 09:31:46 | statement_timeout affects query results fetching? |
| Previous Message | Noah Misch | 2015-08-08 06:30:44 | Re: Raising our compiler requirements for 9.6 |