PostgreSQL 9.2 official release

Today, 10 September 2012, was officially released the release of PostgreSQL 9.2!

/ > Finally ended a long period of beta testing, announced in may this year. The developers promise even greater performance, scalability and flexibility (performance, scalability and flexibility).

performance and scalability


Postgres now supports the 64-core processors, and lowered his Postgres'a, power consumption. Then I suspect everything is clear and without superfluous retreats.

The mechanism of index-only scan. That for an animal such? The fact that the indices in the Postgres database does not provide information about visibility of record. That is, to understand visible to any entry, the server must read the real table the tuple (tuple). There are times that the index contains information about obsolete tuple. It is clear and the horse that access sorted index for much faster access to real table, which can be smeared somehow. Briefly, in version 9.2 this feint ears are possible. Although the index is still no information about visibility of record, the developers have implemented the so-called "map view" (visibility map). Says math: "Visibility map was long ago. In the new release made it resistant to falls of the server, respectively, is guaranteed correct." All this and more is described in detail in Wiki.

Improved and polished Streaming Replication (Streaming Replication). For more details please join in all the same Wiki.

Sweet. Appeared native support for JSON. Web developers are overjoyed and throw caps in the air. The server checks the validity of incoming data, tells where the error, if any, contains the full bunch of functions to convert from/to JSON. For example, array_to_json and row_to_json — just happiness for the lazy, which I most certainly am.

And as for me, the most damning feature was the support of range types (Range Types). I don't know how you could live without them before.

First, ranges can be both discrete and continuous. Discrete should include built-in types such as int4range, int8range and date4range. To continuous, respectively, numrange, tsrange, tstzrange (ts — timestamp, num — numeric).

Second, the range can be open... Remember about square and round brackets? [1;1] is closed and [1;1) — open to the right, etc.

Thirdly, the range can be∞, which is ∞! Remember the anecdote about the first grader?
- Dad, and how eight you spell that?
- Infinity rotated by π/2.

If someone does not understand why I'm so Jolly and play the harmonica, you previously had to use two fields to store such data. And then you and the operators, and indexes, and constraints (constraints)...

Measure?


In the official text are the following comparative numbers from previous versions:
the
    the
  • up To 350,000 read queries per second (4 times faster)
    • the
  • Index-only scan can produce an increase in speed from 2 to 20 times
    • the
  • up To 14,000 data records per second (5 times faster)


Don't know how much it is worth according to puzomerka, because most likely the results obtained on synthetic measurements, but still...
Article based on information from habrahabr.ru

Комментарии

Отправить комментарий

Популярные сообщения из этого блога

Integration of PostgreSQL with MS SQL Server for those who want faster and deeper

Изображение
Recently habré was already published integration PostgreSQL and MSSQL. But, items there is categorically not enough. Therefore, the objectives of this publication are the following: the the to broaden and deepen publicly available information about FDW for MSSQL-called tds_fdw to tell the difference in major versions and describe basic compatibility issues; the to talk about the possibilities of optimization of queries that use the foreign table; the to address the subject of caching external data in a materialized view; the to say a few words about the exotic ways to integrate PostgreSQL and MSSQL. the Installing and configuring TDS FDW The guys from PostgresPro already sufficiently said about this process, I will not repeat. Will leave a few links to the official PostgreSQL documentation and examples from tds_fdw: the the creating an extension (extension) in PG: off.dokumentacija ; the server: off.documentation , example of tds_fdw ; the creating
Далее...

Parse URL in Zend Framework 2

Objective: the Have a method to disassemble the components of the string containing the URL. The string can contain both absolute and relative URLS and both these options should be correctly parsed. the And in the drain, let's say the "wrong" format absolute links without "http://". Further in the text links to the "wrong" format will be called partial absolute references . the Implement support for the "RF" domain. the Example: site.ru/page.php /page.php site.ru/page.php the scheme http the host site.ru site.ru the path page.php page.php page.php Implementation of paragraphs 1 and 2 of our problem In this we should help the class Zend\Uri\Http . He has we need methods parse($uri) , getHost() , getPath() , etc. But! When we parse the URL and type " site.ru/page.php " (without the " http:// ") getHost() will return an empty string and getPath()
Далее...

Custom database queries in MODx Revolution

This topic will certainly be useful for those who have quite a lot of projects on MODx Revolution, as with the usual sites of business cards is enough and the standard working methods of a La $modx- > getObject() , $modx->getCollection() , etc., and these methods are inherently not just a job database, but also with the objects of MODx. When working with large projects methods a La $modx- > getCollection() for us is not the best solution for two reasons: 1. The overexpenditures. These methods are not just getting data from DB, but also create instance of the retrieved objects. In this case, getting information about 10000 documents, we get 10000 objects of modResource that it is not very cool. 2. The task is complicated by the count of records. In addition to the direct difficulties of counting even at the query level, even if you get 10 records of the same document (for example), MODx will return as a result only one object modResource. Although often that will su
Далее...