On Sat, Apr 11, 2015 at 12:56 AM, Peter Eisentraut <
peter_e@gmx.net> wrote:
>
> On 4/9/15 8:58 PM, Petr Jelinek wrote:
> > Well, you can have two approaches to this, either allow some specific
> > set of keywords that can be used to specify limit, or you let sampling
> > methods interpret parameters, I believe the latter is more flexible.
> > There is nothing stopping somebody writing sampling method which takes
> > limit as number of rows, or anything else.
> >
> > Also for example for BERNOULLI to work correctly you'd need to convert
> > the number of rows to fraction of table anyway (and that's exactly what
> > the one database which has this feature does internally) and then it's
> > no different than passing (SELECT 100/reltuples*number_of_rows FROM
> > tablename) as a parameter.
>
> What is your intended use case for this feature? I know that "give me
> 100 random rows from this table quickly" is a common use case, but
> that's kind of cumbersome if you need to apply formulas like that. I'm
> not sure what the use of a percentage is. Presumably, the main use of
> this features is on large tables. But then you might not even know how
> large it really is, and even saying 0.1% might be more than you wanted
> to handle.
>
The use case for specifying number of rows for sample scan is valid
and can be achieved by other means if required as suggested by Petr
Jelinek, however the current proposed syntax (w.r.t to Sample
Percentage [1]) seems to comply with SQL standard, so why not go
for it and then extend it based on more use-cases?
[1]
SQL Standard (2003) w.r.t Sample Percentage
<sample clause> ::=
TABLESAMPLE <sample method> <left paren> <sample percentage> <right paren>
[ <repeatable clause> ]
<sample percentage> ::= <numeric value expression>