>I got the segmentation fault when I tested the case where the least-executed >query statistics is discarded, i.e., when I executed different queries more than >pg_stat_statements.max times. I guess that the patch might have a bug.
Thanks, will try to fix it.
>pg_stat_statements--1.1.sql should be removed. Yes will do that
>+ <entry><structfield>queryid</structfield></entry> >+ <entry><type>bigint</type></entry> >+ <entry></entry> >+ <entry>Unique value of each representative statement for the >current statistics session. >+ This value will change for each new statistics session.</entry>
>What does "statistics session" mean? The time period when statistics are gathered by statistics collector without being reset. So the statistics session continues across normal shutdowns, but in case of abnormal situations like crashes, format upgrades or statistics being reset for any other reason, a new time period of statistics collection starts i.e. a new statistics session. The queryid value generation is linked to statistics session so emphasize the fact that in case of crashes,format upgrades or any situation of statistics reset, the queryid for the same queries will also change. Will update documentation clearly explain the term statistics session in this context
