Re: Wording in TABLESAMPLE documentation - Mailing list pgsql-docs

From Simon Riggs
Subject Re: Wording in TABLESAMPLE documentation
Date
Msg-id CANP8+jK66dJD4+MZk4M1EW0jrUAUVkqrAWnmZfXUXZaCmr4A7w@mail.gmail.com
Whole thread Raw
In response to Re: Wording in TABLESAMPLE documentation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Wording in TABLESAMPLE documentation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-docs
On 12 August 2016 at 16:23, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
>> But now you mention it, I agree with you. Let's put it back to say
>> "sample" but also explain where that new sample comes from... my
>> attempt to explain this better is in square brackets
>
>> "If REPEATABLE is not given then a new random sample will be taken for
>> each query [based upon the global seed value for the current user.]"
>
> I think "global" might have implications we don't want.  How about
> adding ", based on a system-generated seed"?

What I was trying to express was that

SELECT setseed(dp);
SELECT * FROM foo TABLESAMPLE ...;
SELECT * FROM foo TABLESAMPLE ...;
SELECT * FROM foo TABLESAMPLE ...;

would yield a repeatable set of samples, similarly repeatable but not
same samples as

SELECT * FROM foo TABLESAMPLE ... REPEATABLE;
SELECT * FROM foo TABLESAMPLE ... REPEATABLE;
SELECT * FROM foo TABLESAMPLE ... REPEATABLE;

so that people understand there is some predictability even without REPEATABLE.

So I don't understand the "based on a system-generated seed", but
maybe I'm missing information.

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-docs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Wording in TABLESAMPLE documentation
Next
From: Tom Lane
Date:
Subject: Re: Wording in TABLESAMPLE documentation