| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Backport of pg_statistics typos fix |
| Date: | 2017-03-02 16:10:30 |
| Message-ID: | 6e7cba41-96c2-57cb-f405-9d5e35286fe6@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/8/17 14:54, Robert Haas wrote:
> BTW, looking at that commit, this change looks to have adjusted this
> from being wrong to still being wrong:
>
> -<listitem><para>Allow pg_statistics to be reset by calling
> pg_stat_reset() (Christopher)</para></listitem>
> +<listitem><para>Allow pg_statistic to be reset by calling
> pg_stat_reset() (Christopher)</para></listitem>
>
> It's true that pg_stat_reset() doesn't reset the nonexistent
> pg_statistics table. But it doesn't reset pg_statistic either. IIUC,
> it resets the data gathered by the statistics collector, which is
> something else altogether.
Fixed
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-03-02 16:24:10 | Re: Transactions involving multiple postgres foreign servers |
| Previous Message | Peter Eisentraut | 2017-03-02 16:03:44 | Re: Faster methods for getting SPI results |