|
| 1 | +Release 1.7.0 |
| 2 | +============= |
| 3 | + |
| 4 | +New features |
| 5 | +------------ |
| 6 | + |
| 7 | +1. Make the code compatible with PostgreSQL server version 17. |
| 8 | + |
| 9 | +2. Do not copy the values of dropped columns into the new table storage |
| 10 | + (file). |
| 11 | + |
| 12 | + So far, only the whole rows (the deleted ones) were considered to |
| 13 | + contribute to the table bloat. Now we also reclaim the space occupied by |
| 14 | + dropped columns. |
| 15 | + |
| 16 | +3. Let the squeeze.squeeze_table function raise ERROR. |
| 17 | + |
| 18 | + So far, the function only inserted record into the squeeze.log table if the |
| 19 | + processing was successful, and into squeeze.errors if it failed. Now, in |
| 20 | + the case of failure, the function also prints out the error message into |
| 21 | + the console. |
| 22 | + |
| 23 | +4. Do not let the squeeze workers run if there is currently no work for them. |
| 24 | + |
| 25 | + For automatic processing, one scheduler worker per database needs to run, |
| 26 | + but the actual squeeze worker is only started if particular table appears |
| 27 | + to be bloated. Once done with the processing, the squeeze worker exits |
| 28 | + instead of waiting for another task. |
| 29 | + |
| 30 | +5. Improved parallelism of the squeeze workers. |
| 31 | + |
| 32 | + Multiple worker processes (one per table) can be used since the release |
| 33 | + 1.6, but so far it was still possible that the work gets serialized due to |
| 34 | + the logical decoding setup. Those limitations have been relaxed in 1.7. |
| 35 | + |
| 36 | +Bug fixes |
| 37 | +--------- |
| 38 | + |
| 39 | +1. Fixed broken setup of "shared memory hooks". |
| 40 | + |
| 41 | + This could cause server crash if other extensions installed their hooks as |
| 42 | + well. (https://github.com/cybertec-postgresql/pg_squeeze/issues/68) |
| 43 | + |
| 44 | +2. Fixed evaluation of the squeeze.max_xlock_time configuration variable. |
| 45 | + |
| 46 | + Due to this bug, pg_squeeze behaved as if the timeout was set to much lower |
| 47 | + value. (The bug had no effect if the variable was set to 0, which is the |
| 48 | + default.) |
| 49 | + |
| 50 | +3. Fixed permissions checks for the squeeze.pgstattuple_approx() function.q |
| 51 | + |
| 52 | + Like with other functions of this extension, the SUPERUSER role attribute |
| 53 | + is not needed for execution. The REPLICATION attribute is sufficient. |
| 54 | + |
| 55 | + |
1 | 56 | Release 1.6.1 |
2 | 57 | ============= |
3 | 58 |
|
|
0 commit comments