|
|
|
|
|
|
by andrewstuart
1859 days ago
|
|
|
Very interesting thanks for the update - how great is the Internet to hear directly from the developer! It's a pity this wasn't listed in the announcement as I think alot of people are interested in this issue. >> Long term, the way to fix this is to come up with a design that doesn't need to freeze at all. Do you know if anyone is turning their attention to this or is it not currently being tackled by anyone? |
|
|
I see the names of a few people that also work on Postgres on this thread. We're not all that hard to get a hold of if you're a user that has some kind of feedback or question, for what it's worth. The culture is very open in that sense.
> Do you know if anyone is turning their attention to this or is it not currently being tackled by anyone?
This is one of the goals of the zheap project. I myself have some very tentative ideas for tackling it within the standard table access method, heapam. I have not specifically committed to working on it on any timeframe. I haven't completely convinced myself that the approach I'm thinking of is truly robust and practicable. It's pretty complicated, especially because I cannot really know what will break and need to be fixed until I spend significant effort on the implementation.