farrokhi/pg_repack
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
343 Commits 1 Branch 0 Tags
Commit Graph

343 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
masahiko
5781aabb61 Merge pull request #107 from MasahikoSawada/change_to_after_trigger 
Change trigger type to AFTER trigger.
 2017-02-22 12:08:32 +09:00
masahiko
b16886d4ea Merge pull request #116 from MasahikoSawada/fix_format_ident 
Change format identifier %lu to UINT64_FORMAT for portability.
 2017-02-22 00:06:01 +09:00
Josh Kupershmidt
0ee4dca044 Merge pull request #115 from cpaelzer/fix-feb2017-pg-microrelease 
Fix 'tablespace' regression test for latest postgres minor releases
 2017-02-21 08:52:18 -05:00
Masahiko Sawada
e8d6b6b97f Change format identifier %lu in pgut.c file. 2017-02-21 12:23:18 +00:00
Masahiko Sawada
b9219be7d8 Change format identifier to UINT64_FORMAT. 
Change it for portability.
 2017-02-21 16:20:38 +09:00
Christian Ehrhardt
02ced4650a
drop Debian specific content from tablespace_2.out 
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
 2017-02-20 09:13:58 +01:00
Christian Ehrhardt
b85831ea65
Add a variant expected output for the 'tablespace' regression test 
The recent stable update changed output for calls to
repack.repack_indexdef with the third arg being NULL.

Output gets an additional "TABLESPACE pg_default". So add
another variant of expected output to cover 9.6.2, 9.5.6,
9.4.11 and 9.3.16.

Stable update at https://www.postgresql.org/about/news/1733/

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
 2017-02-15 11:30:58 +01:00
Josh Kupershmidt
dfbedb63d9 Merge pull request #110 from MasahikoSawada/change_format_identifier 
Change format identifier of SPI_processed to uint64.
 2017-02-02 22:36:47 -05:00
Masahiko Sawada
bacf197a7b Change format identifier of SPI_processed to uint64. 
Because commit 23a27b039d94ba359286694831eafe03cd970eef has extended the
type of SPI_processed from uint32 to uint64, pg_repack emit warning when
compiling with PostgreSQL 9.6 or later. To fix that, we cast it to uint64
and change format identifier from %d to %lu.
 2017-02-02 23:42:44 +09:00
Masahiko Sawada
375f03c0c3 Change trigger name from a_repack_trigger to repack_trigger. 
In AFTER trigger context, since triggered tuple is not changed by
any other triggers we can call it just repack_trigger.
 2017-01-24 14:09:05 +09:00
Masahiko Sawada
d83ee3d6a0 Change trigger type to AFTER trigger. 
During repacking table, if a transaction executes INSERT CONFLICT
ON UPDATE/DO NOTHING, because we define BEFORE trigger on target
table, the contents of operation log table becomes inconsistent
easliy. As a result, pg_reapck fails with a high probability.

To resolve this issue, this changes the trigger type from BEFORE
to AFTER. We define AFTER trigger that is the first of the AFTER
trigger to fire on the table.
 2017-01-19 16:32:54 +09:00
Josh Kupershmidt
e1056c003c Merge pull request #104 from MasahikoSawada/support_9_6 
Add 9.6 to list as a supported Postgres version.
 2017-01-17 08:54:33 -05:00
Masahiko Sawada
6cadd7d97d Add 9.6 to list as a supported Postgres version. 
Since 9.5 is not listed yet in pg_repack_jp.rst added 9.5 as well.
 2017-01-17 14:28:21 +09:00
Josh Kupershmidt
8711ae5b2a Merge branch 'master' of github.com:reorg/pg_repack 2016-08-05 13:26:18 -07:00
Josh Kupershmidt
6e9ccbd8a0 Remember to list 9.5 as a supported Postgres version. 2016-08-05 13:25:08 -07:00
Josh Kupershmidt
8db0f58daf Merge pull request #87 from postgrespro/vacuum_fix 
Don't wait for concurrent vacuums
 2016-08-05 13:12:06 -07:00
Alexander Korotkov
8e50927946 Comment about VACUUM. 2016-07-03 22:42:17 +03:00
Alexander Korotkov
3b0ef954cf Fix. 2016-07-03 21:19:45 +03:00
Josh Kupershmidt
fe659b0e4a Version bump for 1.3.4 2016-05-07 09:44:26 -04:00
Josh Kupershmidt
b8b18c0cc9 Prep release notes for release 1.3.4. 2016-05-07 09:43:28 -04:00
Josh Kupershmidt
602bf2944a .gitignore for lib/exports.list 2016-05-07 09:25:30 -04:00
Josh Kupershmidt
eb2e9c39fb Whitespace cleanup. 2016-05-07 09:24:05 -04:00
Josh Kupershmidt
de060af137 Merge branch 'medallia-medallia_xlock_for_drop' 2016-05-07 09:20:23 -04:00
Edwina Lu
dcce8e43e9 grab exclusive lock before dropping table 2016-04-15 14:34:41 -07:00
Josh Kupershmidt
0d84624b92 Merge pull request #74 from amitlan/update-release-notes 
Add release notes for 1.3.2 and 1.3.3 releases.
 2016-02-27 16:20:20 -05:00
amit
abb6f002e7 Add release notes for 1.3.2 and 1.3.3 releases. 2016-02-26 10:54:01 +09:00
Josh Kupershmidt
7238a15a9c Merge pull request #72 from j16sdiz/patch-1 
Do not repack unlogged tables (close #71)
 2016-02-16 16:54:05 -05:00
Daniel Cheng (鄭郁邦)
71f8833958 Do not repack unlogged tables (close #71) 2016-02-12 18:50:45 +08:00
Josh Kupershmidt
1b5fd1ae70 Bump version to 1.3.3 2016-02-07 17:58:18 -05:00
Josh Kupershmidt
766722f2fe Merge branch 'amitlan-reg-tests-relopt-quote-fix' 2016-01-24 17:56:20 -05:00
Josh Kupershmidt
4002b4e18f Add a variant expected output for the 'repack' regression test 
so that older versions of Postgres (pre-c7e27bec) will still
pass tests.

Also fix the 'tablespace' test the same way.
 2016-01-24 17:54:48 -05:00
amit
ab70a010a5 Fix regression test output. 
Upstream changes now cause reloption values to be emitted with surrounding
quotes. That breaks, for example, the output of \d commands in one of the
tests.
 2016-01-19 09:30:10 +09:00
amit
e4033c273e Need to #include pg_am.h directly now to use BTREE_AM_OID. 
Due to upstream changes to the index AM API definitions.
 2016-01-18 20:55:57 +09:00
Josh Kupershmidt
668e44e256 Merge pull request #61 from bwtakacy/jp-doc 
Add doc in Japanese
 2015-12-14 15:33:32 -05:00
bwtakacy
b0be609adf Add doc in Japanese 2015-12-07 12:32:13 +09:00
Josh Kupershmidt
2b3a026372 Merge pull request #56 from amitlan/issue-55-fix 
Make repack_drop() processing robust against deadlocks.
 2015-12-02 23:58:48 -05:00
amit
cbe027289a Consider schemaname too when doing LOCK TABLE in repack_drop(). 
This was an oversight in a previous commit to fix the deadlock reported
in Github issue #55.
 2015-12-03 13:32:03 +09:00
Josh Kupershmidt
87dca1c85c Merge pull request #59 from bwtakacy/change_exit_code 
Change exit code for --help and --version.
 2015-11-30 10:14:46 -05:00
bwtakacy
70eac9ee06 Change exit code for --help and --version. 
Previously, it is 1 but the reason is not clear.
It seems to be a historical one because pg_reorg
has the same exit codes.
 2015-11-26 21:51:09 +09:00
amit
94232991b9 Expand a comment in repack_drop(). 
Previous text did not sufficiently explain why taking a lock on the
target table would be necessary.
 2015-11-09 15:23:45 +09:00
amit
5317f527f4 Make repack_drop() processing robust against deadlocks. 
Concurrent activity on the target table can cause deadlocks when
repack_drop() is doing its job, ie, dropping the temporary objects
created. It is highly likely to occur when pg_repack is interrupted
midway through its processing.
 2015-11-06 17:10:13 +09:00
Josh Kupershmidt
20a679b7fb Merge branch 'decibel-Fix-repack_apply-count-bug' 2015-10-14 09:39:55 -04:00
Josh Kupershmidt
5476a416fc Merge branch 'Fix-repack_apply-count-bug' of https://github.com/decibel/pg_repack into decibel-Fix-repack_apply-count-bug 2015-10-14 09:39:46 -04:00
Josh Kupershmidt
f564292e6e Merge branch 'bwtakacy-remove_build_warn' 2015-10-14 09:37:34 -04:00
Josh Kupershmidt
b53b1832bc Merge branch 'remove_build_warn' of https://github.com/bwtakacy/pg_repack into bwtakacy-remove_build_warn 2015-10-14 09:34:09 -04:00
Josh Kupershmidt
f258925f23 .gitignore tweak 2015-10-14 09:11:50 -04:00
Jim Nasby
0e24283856 repack_apply(): Use default if count is negative 
Per documentation, a negative value for count should result in using DEFAULT_PEEK_COUNT.
 2015-10-11 16:39:35 -05:00
bwtakacy
c3960cd118 Include a new header file to build with PostgreSQL 9.5 
By commit 7b1c2a0f2066672b24f6257ec9b8d78a1754f494 in PostgreSQL,
builtins.h is splitted to a new header file ruleutils.h.
The usage of pg_get_indexdef_string in lib/repack.c is affected.
 2015-10-09 13:15:30 +09:00
Josh Kupershmidt
f255a4175d Bump version to 1.3.2 2015-08-13 22:15:30 -04:00
Josh Kupershmidt
facbcf90dd Wrong precedence for these chained less-than / greater-thans. 2015-07-24 07:27:30 -04:00