News for hackers. Stuff that matters.

A comment on A new storage engine for PostgreSQL to provide better control over bloat.

Re:A new storage engine for PostgreSQL to provide better con... by _pj_ on Tuesday March 06, 2018 @04:13AM (#16527771)
I really wish the EDB guys (both Robert Haas and Amit Kapila) would mention in their blog posts about this feature that it's meant to use the pluggable storage API which is also slated for PG12. That would make it more clear that we are not abandoning the current storage format, just giving users choice (per table) to use what works best for their use case. It would also alleviate the worries that some comments expressed for both of the blog posts.
[ Parent | on HN ]
Re:A new storage engine for PostgreSQL to provide better con... by amitkapila on Tuesday March 06, 2018 @08:25AM (#16528652)
To me that was obvious, but you are right, it is better to be clear. I have added a below sentence my blog post.

"I would like to mention that the above results don't mean that zheap will be better in all cases than heap. For example, rollbacks will be costlier in zheap. Just to be clear, this storage format is proposed as another format alongside current heap, so that users can decide which storage they want to use for their use case."

[ Parent | on HN ]
Re:A new storage engine for PostgreSQL to provide better con... by fanf2 on Tuesday March 06, 2018 @06:32AM (#16528182)
Where can we find a summary of the pluggable storage API?
[ Parent | on HN ]
Re:A new storage engine for PostgreSQL to provide better con... by _pj_ on Tuesday March 06, 2018 @06:46AM (#16528225)
I don't think there is a good summary, it hasn't been settled yet. The (rather lengthy) discussion is like with everything on -hackers mailing list - https://www.postgresql.org/message-id/flat/20160812231527.GA...
[ Parent | on HN ]