Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PostgreSQL 9.6 Released

postgresql.org

Post reply on HN
Print view View original

121–130 of 136 posts

Re: PostgreSQL 9.6 Released

#121

Post by asimuvPR »

batmansmk wrote: post #118
fabian2k wrote: post #17

Just from reading the documentation, the full text search features on Postgres already look pretty powerful. And it is encouraging that they are actively being worked on. I'm wondering how this compares to a dedicated search engine like Solr or Elasticsearch. Are there huge differences in performance, features or search quality? At which scale does using Postgres for full text search still make sense?

We have been using Postgres Full Text Search for about 3 years now in production. The app is an analytics dashboard, over a set of structured and unstructured data. We have about 20M documents, with hierarchies, dimensions, but also free text elements. It does work extremely well, and having the possibility to group by as one would do in SQL is a god send for tabular or graph based data. Performance are really good,…

Mind sharing a table structure from your db? I'm using ES for a project and would prefer to keep things simple (already use postgres in another part of the system).

Re: PostgreSQL 9.6 Released

#123

Post by zejn »

pgaddict wrote: post #113
anarazel wrote: post #112

Earlier quoted context omitted.

> There's still only one major PostgreSQL release per year. Well, due to the delayed 9.5 release (January 7th), there have been two this year ;)

Well, that really depends on where exactly you place start of a year ;-) Chinese New Year was February 8, 2016. Orthodox New Year was January 14, 2016. So it's 2:1 for me.

Well, to the best of my knowledge I think PostgreSQL currently only supports Gregorian calendar system ... ;)

Re: PostgreSQL 9.6 Released

#124

Post by evanelias »

MustardTiger wrote: post #120
evanelias wrote: post #87

Earlier quoted context omitted.

You may be confusing InnoDB with MyISAM (which is prone to corruption, especially upon crashes) or with running MySQL without a strict SQL mode (which causes bad things like silent truncation of overflowing values). InnoDB is, and always has been, a very reliable and durable storage engine with solid performance characteristics.

No, I am referring to innodb, which has a number of known reliability problems which are "wontfix".

Care to share examples?

Re: PostgreSQL 9.6 Released

#125

Post by ngrilly »

fabian2k wrote: post #17

Just from reading the documentation, the full text search features on Postgres already look pretty powerful. And it is encouraging that they are actively being worked on. I'm wondering how this compares to a dedicated search engine like Solr or Elasticsearch. Are there huge differences in performance, features or search quality? At which scale does using Postgres for full text search still make sense?

It looks like Postgres Professional is working on improving FTS. Here is a relevant presentation from Oleg Bartunov about the new RUM index and its benefits for FTS:

http://www.sai.msu.su/~megera/postgres/talks/pgopen-2016-rum...

Re: PostgreSQL 9.6 Released

#126

Post by [deleted] »

mslate wrote: post #56
snowwolf wrote: post #32

Please can the Postgres team put some major focus on completing logical replication [1]. It's the missing piece to making upgrading across major versions painless and quick on large databases so that we can take advantage of all these nice new features. We're on a Heroku's hosted Postgres service so can't install the pglogical extension. 1. http://blog.2ndquadrant.com/why-logical-replication/

I don't think you would be able to take advantage of logical replication on Heroku Postgres regardless--they don't allow you to replicate to your own instances, only other Heroku-hosted instances. This makes migrating off Heroku for Postgres a PITA and requiring down-time.

[deleted]

Re: PostgreSQL 9.6 Released

#128

Post by nnutter »

anewhnaccount wrote: post #117
nnutter wrote: post #115

Earlier quoted context omitted.

Are there any good options to support logic (and/or) and facets/fields with Postgres? We started using ES basically just for the "free" query language. (Obviously we would want something that is safe from sql injection.)

SQL supports logic. Either escape manually, use the templating in your driver or use an ORM.

So, "No".
Post reply on HN