Commit Graph

25 Commits (a1387f4aa814afcc8d26cfec36d2006a486d18fa)

Author SHA1 Message Date
Burak Yucesoy 29a4f88b55 Add CHANGELOG entry for 7.0.2 2017-09-28 10:26:28 -07:00
Burak Yucesoy 05678c3a3b Add CHANGELOG entry for 6.2.4 2017-09-28 10:24:48 -07:00
Burak Yucesoy ba31e35791 Add CHANGELOG entry for 6.1.3 2017-09-28 10:07:31 -07:00
Burak Yucesoy 18b9be3dfa Add CHANGELOG entry for 7.0.1 release 2017-09-12 17:52:09 -06:00
Burak Yucesoy 9e89eaa57e Add CHANGELOG entry for 7.0 release 2017-08-28 16:19:24 +03:00
Burak Yucesoy 79c14f73fa Add CHANGELOG entry for 6.2.3 2017-07-12 23:50:54 -06:00
Brian Cloutier 7ad95b53d2 Rename pg_dist_shard_placement -> pg_dist_placement
Comes with a few changes:

- Change the signature of some functions to accept groupid
  - InsertShardPlacementRow
  - DeleteShardPlacementRow
  - UpdateShardPlacementState

- NodeHasActiveShardPlacements returns true if the group the node is a
  part of has any active shard placements

- TupleToShardPlacement now returns ShardPlacements which have NULL
  nodeName and nodePort.

- Populate (nodeName, nodePort) when creating ShardPlacements
- Disallow removing a node if it contains any shard placements

- DeleteAllReferenceTablePlacementsFromNode matches based on group. This
  doesn't change behavior for now (while there is only one node per
  group), but means in the future callers should be careful about
  calling it on a secondary node, it'll delete placements on the primary.

- Create concept of a GroupShardPlacement, which represents an actual
  tuple in pg_dist_placement and is distinct from a ShardPlacement,
  which has been resolved to a specific node. In the future
  ShardPlacement should be renamed to NodeShardPlacement.

- Create some triggers which allow existing code to continue to insert
  into and update pg_dist_shard_placement as if it still existed.
2017-07-12 14:17:31 +02:00
Jason Petersen a1e44328b2
Add 6.2.2 CHANGELOG entry 2017-05-31 17:02:41 -06:00
Jason Petersen eaa9dabad1
Add 6.1.2 CHANGELOG entry 2017-05-31 17:02:24 -06:00
Jason Petersen b072708802
Bump CHANGELOG for 6.2.1 2017-05-24 13:30:36 -06:00
Burak Yucesoy b94285c575
Update CHANGELOG for v6.2.0
CHANGELOG changes for 6.2 release
2017-05-16 22:28:53 -06:00
Jason Petersen 8e2dd3e1f3
Update CHANGELOG for v6.1.1 2017-05-04 17:49:57 -07:00
Jason Petersen bc21da6f6f Add 6.1.0 CHANGELOG entries (#1219)
This is probably missing some stuff, but is my edit of the initial list
compiled by Burak.

cr: @craigkerstiens
2017-02-09 17:05:17 -07:00
Burak Yucesoy 5e5dc2a1cb Add 6.0.1 CHANGELOG entry
Couple fixes and improvements to existing behavior.
2016-11-29 08:05:36 -08:00
Jason Petersen 217f899816
Bump CHANGELOG release dates
Oops.
2016-11-07 09:51:18 -07:00
Jason Petersen e7aeb9865e
Add 6.0.0 CHANGELOG entry
For the upcoming release.
2016-11-07 09:41:08 -07:00
Jason Petersen 24033a6d0b
Add 5.2.2 CHANGELOG entry
Many fixes and improvements to existing behavior.
2016-11-07 09:41:08 -07:00
Jason Petersen be113e99cc
Add 5.2.1 CHANGELOG entry
Outer join and memory leak fixes
2016-09-06 11:45:37 -05:00
Jason Petersen b59ab75e2b
Add 5.2.0 CHANGELOG entry
Our longest yet!
2016-08-15 12:55:12 -06:00
Metin Doslu 3ff1877108
Bump version numbers for 5.2 release 2016-08-01 13:48:24 -07:00
Jason Petersen 88da69df8a
Add CHANGELOG entries for 5.1.1 release
cr: @sumedhpathak
2016-06-17 16:03:32 -06:00
Jason Petersen a7ae634750
Add CHANGELOG entries for 5.1 release
Probably a superset of what we actually want, but should be complete.
2016-05-17 10:02:05 -06:00
Jason Petersen d76ead817b
Add latest CHANGELOG entries 2016-05-10 11:57:00 -06:00
Jason Petersen eab60e20de
Add CHANGELOG entry for 5.0.1 2016-05-04 22:07:43 -06:00
Jason Petersen f9e2e50e4f
Add CHANGELOG 2016-03-23 17:28:16 -06:00