postgresql: All content tagged as postgresql in NoSQL databases and polyglot persistence
PostgreSQL 9.4 will replace the default JSON column type with Hstore.
PostgreSQL 9.4 will be reintroducing Hstore as the column type of choice for document-style data. This supersedes PostgreSQL’s JSON support which was introduced in version 9.0. Being a string-based representation, JSON is significantly slower than the binary structure of HStore. And with the addition of Boolean and integer support, the new Hstore is semantically equivalent to JSON. In practical terms this allows two-way conversions between the formats using just a casting operator.
Amazon RDS adds (beta) support for PostgreSQL.. Pretty much everything is supported, including PostGIS.
Original title and link: Two more things about PostgreSQL ( ©myNoSQL)
As I linked earlier today to the MemSQL and JSON story, I’ve thought again about PostgreSQL and its community approach of bringing in new features. It’s hard to miss what they are doing. And I think they are doing it right.
The PostgreSQL community is looking outside the box and listens. What features are users of NoSQL databases most excited about? Can we offer native support for them? Can we integrate with these other tools? These are the right questions to ask when considering expanding outside your space to help your users.
While it might sound easy to watch what others are doing and then do it yourself—this is probably well-known as the Microsoft strategy—the reality is there’s a lot of complexity of following this strategy. Besides asking the right questions when picking what features to bring in, there are always the technical and design decisions:
- can we actually support this?
- can we support it in a way that’ll not break or impact negatively existing features?
- how should we expose these “imported” features so we make them appealing to existing users (with their vision of the product), while keeping them attractive and familiar to new users?
The last question is the most difficult to come with the right answers.
✚ Here’s also a post I’ve linked to showing how to use PostgreSQL as a schemaless database.
Original title and link: PostgreSQL and the NoSQL world ( ©myNoSQL)
A very interesting set of slides from Christophe Pettus looking at the features in PosgreSQL that would allow one to use it as a document database:
- built-in type
- can handle very large documents (2GB)
- XPath support
- export functions
- no indexing, except defining custom ones using expression index
- hierarchical storage type
- in contrib (not part of the core)
- custom functions (nb: very ugly syntax imo)
- GiST and GIN indexes (nb: I’ve posted in the past about PostgreSQL GiST and GIN Index Types)
- supports also expression indexes
- built-in type starting with PostgreSQL 9.2
- validates JSON
- support expression indexing
- nothing else besides a lot of feature scheduled for
Christophe Pettus’s slides also include the results and some thoughts about a locally-run pseudo-benchmark against these engines and MongoDB.
You can see all the slides and download them after the break.
Original title and link: PosgreSQL as a Schemaless Database ( ©myNoSQL)