Re: Create a separate test file for exercising system views

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Create a separate test file for exercising system views
Date: 2017-01-29 21:12:19
Message-ID: 20170129211219.nauhnm6uhcisysrq@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

Hi,

On 2017-01-29 16:02:21 -0500, Tom Lane wrote:
> I did not do anything about testing the various pg_stat_xxx views.
> Those could be added later, or maybe they deserve their own home.
> (In many cases, those would need something smarter than the basic
> count(*) technique used here, because the C functions are invoked
> in the view's SELECT list not in FROM, so the planner would throw
> away those calls.)

I've previously wished there were a portable equivalent of \o /dev/null
that'd not be perfect, but it'd still exercise more than what we
currently have. Alternatively casting the entire row to text should
allow to use count(*) trickery in some of the cases at least.

> Comments/objections?

Sounds like a good idea here.

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2017-01-29 21:34:00 Re: Performance improvement for joins where outer side is unique
Previous Message David Rowley 2017-01-29 21:07:04 Re: CONNECTION LIMIT and Parallel Query don't play well together