On Tue, Apr 4, 2017 at 9:05 PM, Robert Haas wrote:
> On Mon, Apr 3, 2017 at 11:57 PM, Amit Langote
> wrote:
>> By the way, wonder if it wouldn't make sense to take the whole Table 28.1.
>> Dynamic Statistics Views into a new section (perhaps before 28.2 Viewing
>> Locks or after), since those vie
On Mon, Apr 3, 2017 at 11:57 PM, Amit Langote
wrote:
> By the way, wonder if it wouldn't make sense to take the whole Table 28.1.
> Dynamic Statistics Views into a new section (perhaps before 28.2 Viewing
> Locks or after), since those views display information different from what
> the statistics
On 2017/04/03 22:32, Robert Haas wrote:
> Right now, the information on wait events is organized into one giant
> table inside
> https://www.postgresql.org/docs/devel/static/monitoring-stats.html#monitoring-stats-views
> -- the wait event type is inserted into the lefthand column of the
> table us
From: pgsql-hackers-ow...@postgresql.org
> [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Robert Haas
> Instead of continuing to repair this every time it gets broken, I propose
> that we break this into one table that lists all the wait_event_type values
> -- LWLock, Lock, BufferPin, Act
Right now, the information on wait events is organized into one giant
table inside
https://www.postgresql.org/docs/devel/static/monitoring-stats.html#monitoring-stats-views
-- the wait event type is inserted into the lefthand column of the
table using moreRows="...", which is awkward to maintain a
