diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/tablesample-method.sgml | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/doc/src/sgml/tablesample-method.sgml b/doc/src/sgml/tablesample-method.sgml index b84b7ba8855..880e42c9509 100644 --- a/doc/src/sgml/tablesample-method.sgml +++ b/doc/src/sgml/tablesample-method.sgml @@ -227,7 +227,7 @@ BeginSampleScan (SampleScanState *node, <para> <programlisting> BlockNumber -NextSampleBlock (SampleScanState *node); +NextSampleBlock (SampleScanState *node, BlockNumber nblocks); </programlisting> Returns the block number of the next page to be scanned, or @@ -262,10 +262,9 @@ NextSampleTuple (SampleScanState *node, numbers in the range <literal>1 .. maxoffset</literal> actually contain valid tuples. This is not normally a problem since the core code ignores requests to sample missing or invisible tuples; that should not result in - any bias in the sample. However, if necessary, the function can - examine <literal>node->ss.ss_currentScanDesc->rs_vistuples[]</literal> - to identify which tuples are valid and visible. (This - requires <literal>node->use_pagemode</literal> to be <literal>true</literal>.) + any bias in the sample. However, if necessary, the function can use + <literal>node->donetuples</literal> to examine how many of the tuples + it returned were vlaid and visible. </para> </note> |