- 25 2月, 2017 4 次提交
-
-
由 Dhanashree Kashid 提交于
Added a test for following scenario: When analyzedb is run without --skip_root_partition flag like below, it should also analyze the root partitions. `analyzedb -d <dbname> -s <schema> -a` The root parition table gets listed only in the report file (and not in any state files), hence added appropriate routines for checking the root partition in the report file. Signed-off-by: NJemish Patel <jpatel@pivotal.io>
-
由 Dhanashree Kashid 提交于
When analyzedb is run without --skip_root_partition flag like below, it should also analyze the root partitions. `analyzedb -d <dbname> -s <schema> --full -a` The expected key format for `leaf_root_dict` used for the check is a tuple form and the result returned from the SQL was a string concatenated with ".". Because of this, candidates could not be matched in the dictionary and we never got the root partition details. Made the appropriate changes in analyzedb so that it will identify and analyze on the root partitions. Signed-off-by: NJemish Patel <jpatel-pivotal@pivotal.io>
-
由 Larry Hamel 提交于
Signed-off-by: NMarbin Tan <mtan@pivotal.io>
-
由 Marbin Tan 提交于
Signed-off-by: NLarry Hamel <lhamel@pivotal.io>
-
- 24 2月, 2017 24 次提交
-
-
由 Daniel Gustafsson 提交于
This was commented out close to 10 years ago so it seems about time to retire this to the attic.
-
由 Daniel Gustafsson 提交于
This applies minor cosmetic cleanup to the partition code stemming from a read-through. There are no functional changes from this: * Remove stale comments and reflow existing ones as well as fix some typos * Remove spurious whitespace * Re-indent and rewrite where the logic isn't clear to improve readability (removing !!(foo) construction).
-
由 Daniel Gustafsson 提交于
There is no gain in calling truncateStringInfo() on a StringInfo which was just inited, it will always be no-op. Remove truncates from the partitioning codepath and save a cycle or two. Also remove two StringInfos where one were unused and the other could be replaced with a pstrdup() call.
-
由 Daniel Gustafsson 提交于
occurances was a surprisingly common typo, fix all findings except one in pg_regress.c which will be fixed in a much larger doc patch as we merge upstream.
-
由 Haozhou Wang 提交于
Compatible S3 services don't always return error with XML body, check it before parsing. Signed-off-by: NPeifeng Qiu <pqiu@pivotal.io>
-
由 Daniel Gustafsson 提交于
The Bizgres name hasn't been used for a very long time, retire the last mentions from the reference documentation.
-
由 Daniel Gustafsson 提交于
Updates the reference documentation for psql to match the main GPDB documentation. This only brings in the bare minimum as this reference page is only used for psql. From report by Github user yanchaozhong.
-
由 yanchaozhong 提交于
-
由 Heikki Linnakangas 提交于
The TINC test tested that if you set gp_default_storage_options to 'checksum=False' and create tables, the tables are created without checksums. We already have tests for that in the 'dsp' test in the main test suite. Add the 'checksum' column to a couple of validation queries in the 'dsp' test, to ensure that it would catch it if setting checksums on/off didn't work.
-
由 Heikki Linnakangas 提交于
These tests are all variations: 1. Open a session to database, do some operations in it like CREATE INDEX, DROP INDEX or REINDEX. 2. In another session, attempt to drop the database. The result is always that dropping the database fails, after a timeout, with error: ERROR: database "reindexdb" is being accessed by other users. That's not a very interesting test case, because you get that same error regardless of what the other backend is doing. It doesn't even need to be doing anything, even an idle session has the same effect. Hence, remove these pointless tests.
-
由 Daniel Gustafsson 提交于
The SOMEFILE:SOMEFUNC construction was removed from atmsort with commit 0bf31cd6, remove leftover rules relying on it still in the error suite (obviously not needed either since the suite still works). This brings the test files a little closer to upstream.
-
由 Heikki Linnakangas 提交于
Some tests in the AOCO compression TINC test suite were run with 1MB and 2MB block sizes. That seems excessive. There is no magic boundary, like e.g. when going from 1 GB to 2 GB, between 1 MB and 2 MB, so it's hard to see how anything would behave differently in any interesting way between those two values. This test suite runs for a very long time, so remove the 1 MB permutations from those cases, to reduce the runtime. (The test files have 1G and 2G in the names, but that is misleading; these tests vary the blocksize option to CREATE TABLE command, between 1MB and 2MB. That's megabytes, not gigabytes. That ought to be fixed, but not in this patch)
-
由 Heikki Linnakangas 提交于
All of these tests were already in the 'partition' test of the main suite, in more or less identical form. I did add one little query to 'partition', to test that START of a partition range cannot be NULL. The existing test only covered "END (NULL)". Also, stop testing for long-gone scripts gpaddpart, gpcreatepart and gpdeletepart utilities.
-
由 Adam Lee 提交于
-
由 Adam Lee 提交于
-
由 Adam Lee 提交于
-
由 Peifeng Qiu 提交于
Signed-off-by: NYuan Zhao <yuzhao@pivotal.io>
-
由 Chris Hajas 提交于
The "Execute on" syntax was added when performing a "\d" on external tables in gpdb5, but is not present in previous gpdb versions. When transferring from clusters on previous versions, we will ignore this syntax.
-
由 Heikki Linnakangas 提交于
There are plenty of VACUUMs on append-only tables elsewhere in the regular regression suite, e.g. in 'vacuum_gp', 'appendonly', 'aocs', uao_compaction tests, and many more.
-
由 Heikki Linnakangas 提交于
Subtransactions with append-only tables are covered at least by the uao_dml/uao_dml_[row|column] tests in the main regression suite.
-
由 Heikki Linnakangas 提交于
These ALTER TABLE commands are covered by the 'alter_table_ao' and 'alter_table_aocs' tests in the main regression suite.
-
由 Heikki Linnakangas 提交于
We have sufficient coverage for these debugging functions in src/test/regress/sql/sql/gp_toolkit_ao_funcs.sql already.
-
由 Ashwin Agrawal 提交于
-
- 23 2月, 2017 12 次提交
-
-
Bad things happen otherwise. One case in point is create database followed by a crash. Create database requests a checkpoint after inserting new tuple into pg_database. Crash happens right after create database commits and before clog update is not flushed to disk. Relcache initialization before xlog replay will set HEAP_XMIN_INVALID hint bit in the newly created database's tuple because clog did not report the xmin as committed.
-
The need for heap access methods before xlog replay is removed by commit e2d6aa1481f6cdbd846d4b17b68eb4387dae9211. This commit simply moves the relcache initialization to pass4, where it is really needed. Do not bother to remove relcache init file at the end of crash recovery pass2. Error out if relation cache initialized at wrong time.
-
由 Ashwin Agrawal 提交于
-
由 Heikki Linnakangas 提交于
There are only a few tests left in "uao", most have now been moved to installcheck-world. The "uao" job now runs in about 4 minutes, of which 2 minutes is spent on setting up the test cluster. That seems like overkill, so simplify things by merging the remaining uao fault injection tests into the larger "storage" job.
-
由 Heikki Linnakangas 提交于
These are the same tests queries for column-oriented append-only tables, as those moved by commit 11a5a807, for row-oriented append-only tables. There were two additional tests that were never executed for row-oriented tables though: phantom_reads_update_serializable and phantom_reads_delete_serializable. I believe that was an oversight in the original test suite; they are now also executed for row-oriented tables. We use the UAO templating mechanism, to run the same test files against row- and column-oriented tables. To make that work, fix a bug in the templating mechanism pg_regress.c: if the --ao-dir argument was shorter than 7 characters, the uao directory was not detected correctly.
-
由 Heikki Linnakangas 提交于
We have sufficient test coverage for gpload in the Behave tests in gpMgmt/test/behave/mgmt_utils. And we have plenty of tests for external tables elsewhere. The combination of using an external table or gpload as the source, and append-only table as the target, is not particularly interesting. So remove the tests.
-
由 Heikki Linnakangas 提交于
-
由 Haozhou Wang 提交于
Update pg_dump, cdb_dump_agent, psql to fix MU tests after ON MASTER patch
-
由 Adam Lee 提交于
cURL automatically adds the CONTENT-LENGTH header when performs "PUT" request, we also did it without this commit, AWS is OK with that, but others would report duplicate CONTENT-LENGTH error. Signed-off-by: NYuan Zhao <yuzhao@pivotal.io>
-
由 Yuan Zhao 提交于
palloc and repalloc will check request size is under MaxAllocSize, but the implementation(AllocSetAllocImpl, AllocSetReallocImpl) allocs ALLOC_BLOCKHDRSZ + ALLOC_CHUNKHDRSZ more bytes to store block information. Later MemoryContextNoteAlloc is called with block size. If palloc request size is between MaxAllocSize - (ALLOC_BLOCKHDRSZ + ALLOC_CHUNKHDRSZ) and MaxAllocSize, an internal error occurs. Fix: simply remove those assertions, the calculations in MemoryContextNoteAlloc and MemoryContextNoteFree should work with larger values. This resolves https://github.com/greenplum-db/gpdb/issues/1090. Signed-off-by: NPeifeng Qiu <pqiu@pivotal.io> Signed-off-by: NYuan Zhao <yuzhao@pivotal.io>
-
由 Adam Lee 提交于
AWS S3 returns internal errors (HTTP response code 500) serveral times, unusual but better not to ignore, this commit re-sends requests when it happens. Signed-off-by: NHaozhou Wang <hawang@pivotal.io>
-
由 Marbin Tan 提交于
* We were accessing a non-existent variable as it's being generated by the later function. Swapping the two methods. * Fix on top of a86e4901
-