You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,7 @@ More interesting features are yet to come. Stay tuned!
35
35
36
36
##Roadmap
37
37
38
+
* Provide a way to create user-defined partition creation\destruction callbacks (issue[#22](https://github.com/postgrespro/pg_pathman/issues/22))
38
39
* Implement LIST partitioning scheme;
39
40
* Optimize hash join (both tables are partitioned by join key).
40
41
@@ -63,7 +64,7 @@ Done! Now it's time to setup your partitioning schemes.
63
64
create_hash_partitions(relation REGCLASS,
64
65
attributeTEXT,
65
66
partitions_countINTEGER,
66
-
partition_nameTEXT DEFAULTNULL)
67
+
partition_nameTEXT DEFAULTNULL)
67
68
```
68
69
Performs HASH partitioning for`relation` by integer key`attribute`. The`partitions_count` parameter specifies the number of partitions to create; it cannot be changed afterwards. If`partition_data` is`true` then all the data will be automatically copied from the parent table to partitions. Note that data migration may took a while to finish and the table will be locked until transaction commits. See`partition_table_concurrently()` for a lock-free way to migrate data.
69
70
@@ -349,7 +350,7 @@ SELECT tableoid::regclass AS partition, * FROM partitioned_table;
349
350
350
351
- All running concurrent partitioning tasks can be listed using the`pathman_concurrent_part_tasks` view:
351
352
```plpgsql
352
-
postgres=#SELECT * FROM pathman_concurrent_part_tasks;
Copy file name to clipboardExpand all lines: README.rus.md
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -38,6 +38,7 @@ More interesting features are yet to come. Stay tuned!
38
38
39
39
##Roadmap
40
40
41
+
* Предоставить возможность установки пользовательских колбеков на создание\уничтожение партиции (issue[#22](https://github.com/postgrespro/pg_pathman/issues/22))
41
42
* LIST-секционирование;
42
43
* Оптимизация hash join для случая, когда обе таблицы секционированы по ключу join’а.
43
44
@@ -65,7 +66,7 @@ CREATE EXTENSION pg_pathman;
65
66
create_hash_partitions(relation REGCLASS,
66
67
attributeTEXT,
67
68
partitions_countINTEGER,
68
-
partition_nameTEXT DEFAULTNULL)
69
+
partition_nameTEXT DEFAULTNULL)
69
70
```
70
71
Выполняет HASH-секционирование таблицы`relation` по целочисленному полю`attribute`. Параметр`partitions_count` определяет, сколько секций будет создано. Если`partition_data` установлен в значение`true`, то данные из родительской таблицы будут автоматически распределены по секциям. Стоит иметь в виду, что миграция данных может занять некоторое время, а данные заблокированы. Для конкурентной миграции данных см. функцию`partition_table_concurrently()`.
71
72
@@ -348,7 +349,7 @@ SELECT tableoid::regclass AS partition, * FROM partitioned_table;
348
349
349
350
- Получить все текущие процессы конкурентного секционирования можно из представления`pathman_concurrent_part_tasks`:
350
351
```plpgsql
351
-
postgres=#SELECT * FROM pathman_concurrent_part_tasks;