tablesample test failure with small TOAST_TUPLE_THRESHOLD

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: tablesample test failure with small TOAST_TUPLE_THRESHOLD
Date: 2016-10-14 16:14:49
Message-ID: CA+TgmoYHfaJobF9PN+2N+PA0evgsQy_RM4gU3LwXmutMRVU+mQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Today, I tried compiling with:

-#define TOAST_TUPLE_THRESHOLD MaximumBytesPerTuple(TOAST_TUPLES_PER_PAGE)
+#define TOAST_TUPLE_THRESHOLD 100

Most of the regression tests pass just fine, but the tablesample one
experiences numerous failures. For example:

SELECT t.id FROM test_tablesample AS t TABLESAMPLE SYSTEM (50) REPEATABLE (0);
id
----
! 3
! 4
! 5
! 6
! 7
! 8
! (6 rows)

SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (100.0/11) REPEATABLE (0);
id
--- 5,11 ----
SELECT t.id FROM test_tablesample AS t TABLESAMPLE SYSTEM (50) REPEATABLE (0);
id
----
! (0 rows)

SELECT id FROM test_tablesample TABLESAMPLE SYSTEM (100.0/11) REPEATABLE (0);
id

Most of the failures are due to table-sampling that previously
returned rows no longer returning any rows. I don't know why that
should happen, or whether it's expected.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-10-14 16:17:25 Re: Re: [COMMITTERS] pgsql: Extend framework from commit 53be0b1ad to report latch waits.
Previous Message Jim Nasby 2016-10-14 16:10:49 Re: Renaming of pg_xlog and pg_clog