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

PostgreSQL 9.3 Beta 1 Released

postgresql.org

Post reply on HN
Print view View original

41–50 of 118 posts

Re: PostgreSQL 9.3 Beta 1 Released

#41

Post by jeltz »

masklinn wrote: post #28
Refefer wrote: post #20

Materialized Views! Well, sort of; it appears they don't automatically refresh when data has been updated in the underlying tables ala Oracle's implementation, but this gets you rather close.

FWIW, since Posgtres has hard version cycles (6 months I believe?) the point was to have a working base out and about, future versions will likely add auto-update: > This is a minimal implementation, but should still be useful in many cases. Currently data is only populated "on demand" by the CREATE MATERIALIZED VIEW and REFRESH MATERIALIZED VIEW statements. > It is expected that future releases will add incremental…

The cycles are 12 months, otherwise you are correct.

Re: PostgreSQL 9.3 Beta 1 Released

#42

Post by mintyfresh »

sickpig wrote: post #35
mintyfresh wrote: post #12

Earlier quoted context omitted.

In that spirit, what are the best resources for getting started and diving in to working with PostgreSQL?

Postgresql documentation is terrific, really [1]. Then you can also use pgsql wiki [2]. Other useful resources are the searchable mailing lists archive [3]. Have a look also to pgcon.org web site, it's fully packed of presentation material (mainly pdf slides) gathered since 2007, just to give you an example look at Tom Lane's " http://www.pgcon.org/2011/schedule/events/350.en.html [4] Speaking of books a few of the b…

Awesome. Thank you for putting this together. It looks like the consensus is the PostgreSQL documentation.

Re: PostgreSQL 9.3 Beta 1 Released

#43

Post by netghost »

masklinn wrote: post #31
btown wrote: post #27

Earlier quoted context omitted.

Where would one find out if anyone is working on a patch for ActiveRecord?

The Rails/ActiveRecord bug tracker? edit: the underlying connector might be a better idea to start with, as it'll need to expose the fields somehow before an ORM can take advantage of them.

This is where you'd want to be looking in the source: https://github.com/rails/rails/tree/master/activerecord/lib/...

Specifically at any error handling, which I think would likely be here:

https://github.com/rails/rails/blob/master/activerecord/lib/...

Re: PostgreSQL 9.3 Beta 1 Released

#44

Post by netghost »

tiwazz wrote: post #17
alberth wrote: post #7

Earlier quoted context omitted.

HStore [1] is NoSQL plugin for Postgres. Works great. Been available for a long time too. [1] http://www.postgresql.org/docs/9.0/static/hstore.html

I don't believe hstore supports nested structures, which would make it less than a drop in replacement for many NoSQL use cases. Native JSON support should fix that though, so good news everyone! http://www.postgresql.org/docs/devel/static/functions-json.h...

hstore is just based on a text format, so if it doesn't support it normally, you could just cast the results of each query to a new hstore, something like `select (data -> foo)::hstore -> bar`.

It's probably not a good idea though ;) You don't get any benefit of indices in that case, and I'm not sure what would happen with nulls.

Re: PostgreSQL 9.3 Beta 1 Released

#45

Post by netghost »

venus wrote: post #10
sickpig wrote: post #8

for a more in depth list of changes / new features look at release note[1] and the wiki 9.3Beta1 page[2] [1] http://www.postgresql.org/docs/devel/static/release-9-3.html [2] http://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9...

Materialised views! Damn, I really could have used that a year and a bit ago..

They're a little less than what you might be expecting since they require you to manually signal when they should be updated, but otherwise they sound pretty great.

Re: PostgreSQL 9.3 Beta 1 Released

#46

Post by snaky »

karavelov wrote: post #34
snaky wrote: post #25

Earlier quoted context omitted.

If there would be HandlerSocket or similar, yes.

Postgresql has prepared queries - they give you the same type of optimization (skip the query parsing on each execution) with more flexibility and with SQL standard syntax.

Prepared statements are far away from speedup you may get with handlersocket, even with https://github.com/dimitri/preprepare

Re: PostgreSQL 9.3 Beta 1 Released

#48

Post by jeffdavis »

So, what's still missing in postgres?

To make the responses as constructive as possible, please also specify:

* Whether you currently use postgres, and what other systems you use (presumably ones that do have the feature that is missing in postgres)

* Whether you currently need the feature, or whether you anticipate the need in the future, or whether you expect that other people will need it

* Whether the missing feature is preventing you from using postgres, or just a significant pain point (which could include ease-of-use issues)

Re: PostgreSQL 9.3 Beta 1 Released

#49

Post by defen »

simonw wrote: post #13

"Indexed regular expression search" How does that work from a computer science point of view? UPDATE: Found this talk about it from PGCon last year: http://lanyrd.com/2012/pgcon/schdzf/

Not sure what PostgreSQL is doing, but this is a useful resource: http://swtch.com/~rsc/regexp/regexp4.html

Re: PostgreSQL 9.3 Beta 1 Released

#50

Post by effn »

btown wrote: post #27
masklinn wrote: post #9

The short log is missing one of the most important and awesome new feature to application writers: a bunch of new PQresultErrorFields[0] on constraint failure, providing access to (context-dependent) the raw schema name, table name, column name, constraint name and datatype involved. Previously these remained locked into the database and to get programmatically-useable info (for logging, better error messages or to t…

Where would one find out if anyone is working on a patch for ActiveRecord?

ActiveRecord doesn't even support constraints in the first place.
Post reply on HN