mirror of
https://github.com/neondatabase/neon.git
synced 2025-12-22 21:59:59 +00:00
3aca717f3d
Merge batch_others and batch_pg_regress. The original idea was to split all the python tests into multiple "batches" and run each batch in parallel as a separate CI job. However, the batch_pg_regress batch was pretty short compared to all the tests in batch_others. We could split batch_others into multiple batches, but it actually seems better to just treat them as one big pool of tests and use pytest's handle the parallelism on its own. If we need to split them across multiple nodes in the future, we could use pytest-shard or something else, instead of managing the batches ourselves. Merge test_neon_regress.py, test_pg_regress.py and test_isolation.py into one file, test_pg_regress.py. Seems more clear to group all pg_regress-based tests into one file, now that they would all be in the same directory.
52 lines
796 B
SQL
52 lines
796 B
SQL
create table foo(a int primary key, b int, c int);
|
|
insert into foo values (generate_series(1,10000), generate_series(1,10000), generate_series(1,10000));
|
|
create index concurrently on foo(b);
|
|
create index concurrently on foo(c);
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
vacuum full foo;
|
|
\d foo
|
|
drop table foo;
|