Received: from sss.pgh.pa.us ([192.204.191.242])
	by postgresql.org (8.11.3/8.11.4) with ESMTP id fA7HmYm15099
	for <pgsql-docs@postgresql.org>; Wed, 7 Nov 2001 12:48:35 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id fA7HmQc05334;
	Wed, 7 Nov 2001 12:48:26 -0500 (EST)
To: Peter Eisentraut <peter_e@gmx.net>
cc: pgsql-docs@postgresql.org
Subject: Re: Example is too wide 
In-reply-to: <Pine.LNX.4.30.0111071748240.835-100000@peter.localdomain> 
References: <Pine.LNX.4.30.0111071748240.835-100000@peter.localdomain>
Comments: In-reply-to Peter Eisentraut <peter_e@gmx.net>
	message dated "Wed, 07 Nov 2001 18:27:59 +0100"
Date: Wed, 07 Nov 2001 12:48:25 -0500
Message-ID: <5331.1005155305@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200111/16
X-Sequence-Number: 1089

Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Lane writes:
>> It's going to be difficult to produce any 80-col-wide examples of any
>> of the interesting columns in pg_stats.  How do you feel about
>> artificially line-breaking the printout?

> I tried the example query on the tenk1 table and got a pretty good output.
> Not only is it only 120 columns, which makes it fit really well into the
> HTML browser window (mine anyway), it also contains more diverse rows
> which can serve the example, e.g., output for unique columns, and a few
> interesting n_distinct values.  I'm tempted to use that one instead.

Well, the thing is that tenk1 is completely artificial data, so the
stats it produces are a tad on the meaningless/uninteresting side.
AFAICT the "road" table is the only realistic sample data we have in
the distribution.

However, I won't argue the point too hard.  If the tenk1 example works
from a formatting point of view, go with it.

			regards, tom lane