88fe6bfa9c
Update Japanese doc for pg_repack 1.4.3 release.
2018-05-22 10:03:27 +09:00
f4e010386a
Preparing release 1.4.3
2018-05-19 17:27:49 +01:00
bf61feefc4
Fix Japanese doc.
2017-10-17 12:16:44 +09:00
4fa4f8945e
Fix change logs of version 1.4.1 and 1.4.2.
2017-10-17 12:11:28 +09:00
fdad0b87a2
Fix Japanese doc.
2017-10-17 18:03:07 +09:00
f789bc965d
Clarify note about GiST indexes
...
As per http://lists.pgfoundry.org/pipermail/reorg-general/2015-May/000306.html
2017-09-29 14:03:02 +13:00
66f5da58c9
Update Japanese doc for the recent changes.
2017-09-25 11:19:22 -07:00
1cb3a52ccb
Changelog updated with last developments
2017-09-25 03:17:00 +01:00
20f5bf4878
Update pg_repack_jp.rst for release 1.4.1.
2017-08-13 00:32:13 +09:00
ea27a94578
Typo fixed (after releasing, of course...)
2017-08-12 13:15:14 +01:00
b2be4741c9
Preparing release 1.4.1
2017-08-12 12:56:43 +01:00
5b1001d620
Fixed info to refresh website, suggest to tag after deployment
2017-04-25 17:58:09 +01:00
2d11efea18
Fixed reST error in Japanese docs
2017-04-25 16:13:53 +01:00
00e66eb735
Fix a typo in pg_repack.rst
2017-04-25 15:21:18 +09:00
317eb849ad
Add a new feature -I option to release note.
2017-04-25 15:18:21 +09:00
5f2904362a
Update Japanese doc for -I option.
2017-04-25 15:15:04 +09:00
e1f362e831
resolve conflicts
2017-04-19 14:05:53 +03:00
6de31a1249
Add new item in Japanese doc.
2017-04-11 23:49:10 +09:00
d55a08fc1e
Merge branch 'master' into toast_storage_param
2017-04-11 23:30:27 +09:00
c75a55d229
Update new item in Japanese doc.
2017-04-11 23:10:08 +09:00
467389abd6
Report column storage issue fixed in docs
...
Close #94 .
2017-04-10 23:31:52 +01:00
3afe19e7c4
Report issue fixed in docs
...
Close #10
2017-04-10 23:21:26 +01:00
9f54321e32
Merge branch 'master' into support_table_inheritance
2017-03-30 13:37:54 +03:00
46dd16a6ed
Dropped doc about non-extension installation
2017-03-29 04:39:02 +01:00
914d1c4b3d
Document supported versions are 9.1 to 9.6
2017-03-29 04:39:02 +01:00
a8fe1fe1ec
Add new features of release 1.4 to Japanese doc.
2017-03-27 19:04:34 +09:00
4e90fe9b48
resolve conflicts
2017-03-24 16:54:16 +03:00
bf550706fc
Add --exclude-extension option to new features.
2017-03-24 17:43:21 +09:00
9422daae7a
Merge branch 'optional_include_extensions' of https://github.com/funbringer/pg_repack into funbringer-optional_include_extensions
2017-03-24 17:38:49 +09:00
81cca1836b
Fixed docs reST formatting
...
In Japanese too! ツ
2017-03-23 18:12:33 +00:00
9bef0d4fa7
Added new features to release 1.4
2017-03-23 17:42:39 +00:00
3419422786
update docs
2017-03-23 16:39:58 +03:00
462c37c57e
Update pg_repack_jp.rst
...
Since v1.3.3, when Japanese doc has been introduced, this
file had not been maintained.
2017-03-23 10:50:02 +09:00
5507a57d05
improve docs
2017-03-22 16:34:08 +03:00
698d1ddfdd
update docs
2017-03-22 16:32:11 +03:00
7471eeaa0c
Merge branch 'master' into no_superuser_check
2017-03-01 08:34:29 -08:00
b329f9e143
Merge pull request #108 from MasahikoSawada/dont_kill_backend
...
Introduce --no-kill-backend option.
2017-02-23 09:39:36 +09:00
d1d3d774d3
Update Japanese documentation for no-kill-backend option.
2017-02-22 06:03:09 +00:00
f6c1304c36
Change the option name to no-kill-backend.
...
For consistency with other slimilar option such as no-order,
no-analyze.
2017-02-22 03:49:04 +00:00
168676b3b6
Introduce --no-superuser-check option.
...
The current client checks for superuser before attempting to
execute pg_repack commands. In Amazon RDS, customers are given
access to a psuedo-superuser role called rds_superuser, but they
are not given access to superuser. However, rds_superusers will
otherwise have the ability to execute pg_repack commands in RDS.
This change introduces the --no-superuser-check option in the
client code so that users can disable the client-side superuser
checks.
2017-02-15 03:15:03 +00:00
34c6506f54
Introduce --dont-kill-backend option.
...
pg_repack needs to take an exclusive lock at the end of the
reorganization. If the lock cannot be taken after duration
--wait-timeout option specified and this option is true,
pg_repack gives up to repack a target table instead of
cancelling conflicting backend. False by default.
2017-01-24 14:47:00 +09:00
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
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
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
6e9ccbd8a0
Remember to list 9.5 as a supported Postgres version.
2016-08-05 13:25:08 -07:00
b8b18c0cc9
Prep release notes for release 1.3.4.
2016-05-07 09:43:28 -04:00
abb6f002e7
Add release notes for 1.3.2 and 1.3.3 releases.
2016-02-26 10:54:01 +09:00
b0be609adf
Add doc in Japanese
2015-12-07 12:32:13 +09:00
8fe2cf1296
Some further fixes/cleanup/wordsmithing of the doc changes.
2015-05-19 20:10:25 -04:00
c375c2009d
wording
2015-05-13 14:47:56 +02:00
