| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Subject: | Re: Freeze avoidance of very large table. |
| Date: | 2015-07-09 00:09:56 |
| Message-ID: | 559DBBD4.6020406@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/8/15 8:31 AM, Simon Riggs wrote:
> I understood.
> So I will place bunch of test like src/test/module/visibilitymap_test,
> which contains some tests regarding this feature,
> and gather them into one patch.
>
>
> Please place it in core. I see value in having a diagnostic function for
> general use on production systems.
+1. I don't think there's value to keeping this stuff away from DBAs.
Perhaps it should default to only SU being able to execute it though.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-07-09 01:50:39 | Re: Improving log capture of TAP tests with IPC::Run |
| Previous Message | Pavel Stehule | 2015-07-08 22:23:27 | Re: PL/pgSQL, RAISE and error context |