| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Remove compliation warning of unitialized value (#413) Co-authored-by: Pavel Seleznev <PNSeleznev@sberbank.ru> | 2 年前 | |
Use a single version number for program, library and SQL Having the SQL on a different numbering scheme is useful to provide an ungrade path. But pg_repack has no need of such a path as it can be uninstalled with no problem, so we are not going to provide update script. Hence it's much easier to have a single version number for everything. | 13 年前 | |
Copyright year bumped | 5 年前 | |
introduce option --parent-table (-I, stands for 'inheritance'), fix function repack_one_database(), introduce function repack.get_table_and_inheritors() | 9 年前 | |
Use a single version number for program, library and SQL Having the SQL on a different numbering scheme is useful to provide an ungrade path. But pg_repack has no need of such a path as it can be uninstalled with no problem, so we are not going to provide update script. Hence it's much easier to have a single version number for everything. | 13 年前 | |
Issue 282: Fix check of NOT NULL by repack.primary_keys (#376) PostgreSQL 11 introduced covering indexes. pg_repack couldn't use indexes which include additional columns because all columns are listed in `pg_index.indkey`. To overcome this it is necessary to consider `pg_index.indnkeyatts` value. | 2 年前 | |
Acquire ACCESS EXCLUSIVE lock on repack_drop() when trigger exists repack_swap() already drops the trigger repack_trigger and repack_drop() doesn't need to drop it if repack_swap() finished successfully. If repack_drop() doesn't need to drop the trigger it also doesn't need to acquire ACCESS EXCLUSIVE lock which might be beneficial on write heavy tables. | 8 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 年前 | ||
| 13 年前 | ||
| 5 年前 | ||
| 9 年前 | ||
| 13 年前 | ||
| 2 年前 | ||
| 8 个月前 |