diff options
| author | Stephen Frost <sfrost@snowman.net> | 2014-04-13 00:41:33 -0400 |
|---|---|---|
| committer | Stephen Frost <sfrost@snowman.net> | 2014-04-13 00:41:33 -0400 |
| commit | b3e6593716efef901fcc847f33256c6b49958898 (patch) | |
| tree | 43e37a207d8e3e812ad97a1e8202ae3066063e6c /src/backend/access/gist | |
| parent | d95425c8b9d3ea1681bd91b76ce73be95ca5ee21 (diff) | |
| download | postgresql-b3e6593716efef901fcc847f33256c6b49958898.tar.gz postgresql-b3e6593716efef901fcc847f33256c6b49958898.zip | |
Add ANALYZE into regression tests
Looks like we can end up with different plans happening on the
buildfarm, which breaks the regression tests when we include
EXPLAIN output (which is done in the regression tests for
updatable security views, to ensure that the user-defined
function isn't pushed down to a level where it could view the
rows before the security quals are applied).
This adds in ANALYZE to hopefully make the plans consistent.
The ANALYZE ends up changing the original plan too, so the
update looks bigger than it really is. The new plan looks
perfectly valid, of course.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions