| |||||||||||||
How 3.6 nearly broke PostgreSQLHow 3.6 nearly broke PostgreSQLPosted Oct 6, 2012 8:13 UTC (Sat) by eternaleye (guest, #67051)In reply to: How 3.6 nearly broke PostgreSQL by Zenith Parent article: How 3.6 nearly broke PostgreSQL
Another option might be to use a Kautz digraph - it seems like in terms of a migration problem like this, it might be very nearly optimal.
I've found this to be a far clearer explanation than the Wikipedia article: http://pl.atyp.us/wordpress/index.php/2007/12/the-kautz-g...
In learning about them myself, I wrote a perl script to generate a Kautz graph: http://ix.io/36j/
It takes the degree as the first argument and the dimension and the second, and outputs a list of edges as <from> <to> tuples, one per line.
I still need to write the Kautz::Graph class (stubbed in the file above) to embody a full set of the Kautz nodes with the same degree and dimension parameters, and see about modifying it to generate dot so it can make a nice graphic.
(Log in to post comments)
How 3.6 nearly broke PostgreSQL Posted Oct 6, 2012 8:26 UTC (Sat) by eternaleye (guest, #67051) [Link]
...And I just realized I misread my own code. It actually prints the names of the nodes, it's just that the symbols of the name are space-separated since they can be any positive integer <= degree.
Well, one more thing to remedy.
How 3.6 nearly broke PostgreSQL Posted Oct 6, 2012 8:45 UTC (Sat) by eternaleye (guest, #67051) [Link]
Alright, here's a version that has a Kautz::Graph class, and prints both nodes and edges when run: http://ix.io/36k/
|
|||||||||||||