1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
Release 2.1
===========
1. Do not try to create NOT NULL constraint unnecessarily.
NOT NULL constraint is automatically created for columns involved in PRIMARY
KEY constraint. Thus if the old table has a NOT NULL constraint in the
catalog, we should only create it on the new table if the related column is
not part of primary key.
While this unnecessary ALTER TABLE ... ADD CONSTRAINT ... NOT NULL command
used to be ignored silently so far, it causes ERROR since PostgreSQL 18.2.
Release 2.0
===========
1. This release makes the extension useful in more use cases.
Besides turning a non-partitioned table into a partitioned one, it can be
used to change 1) data type of column(s), 2) order of columns, 3)
tablespace.
2. A single function `rewrite_table()` is used now to handle all the use
cases.
3. Constraints are handled in a more convenient way.
The extension now takes care of creating the constraints on the target
table according to the source table. The user only needs to validate the
constraints after the rewriting has finished.
Unlike the previous release, the rewritten table can be referenced by
foreign key constraints.
Note: The `rewrite.check_constraints` configuration variable was
removed. If there is a risk that other users could run `ALTER TABLE` on
the table during rewriting, please revoke the corresponding privileges
from them temporarily.
Release 1.1.1
=============
This release only adjusts the code so it is compatible with PostgreSQL server
version 17.
Release 1.1.0
=============
New Features
------------
1. Make the code compatible with PostgreSQL server version 16.
2. Added progress monitoring.
|
