Today PostgreSQL Global Development Group declared PostgreSQL 9.5 output. Among other innovations it is possible to note the UPSERT function, safety at the level of lines (Row Level Security, RLS) and several functions of work with Big Data. According to developers, new functions do PostgreSQL by the best option among all possible for startups, big corporations, the government organizations.
As such, there's really no "standard" benchmark that will inform you about the best technology to use for your application. Only your requirements, your data, and your infrastructure can tell you what you need to know.
For a start there is a little philosophy. NoSql surrounds and not to escape from it anywhere (though not really that and there was a wish). Let's leave questions of the deep reasons beyond the scope of this text, we will note only that this trend is reflected not only in emergence of new NoSql of solutions and development of old. One more edge — mixing of contrasts, namely support of storage of schema-less of data in traditional relational bases. In this gray area on a joint of a relational model of data storage and all the rest the dizzy quantity of opportunities is covered. But, as well as always, it is necessary to be able to find balance which is suitable for your data. It can be difficult, first of all because it is necessary to compare a little comparable things, for example, solution NoSql performance to the traditional database. In this small note such attempt will be offered and performance comparison of work with jsonb is given in PostgreSQL with json in Mysql and with bson in Mongodb.
1 year, 9 months agoIn PostgreSQL, unfortunately, yet not many actively use function of a partitsionirovaniye of tables. In my opinion, very adequately tells about it in the work of Hubert Lubaczewski (depesz.com). I offer you one more transfer of its article!
Recently I noticed that I in increasing frequency face cases where it would be possible to use a partitsionirovaniye. And though, theoretically, most of people knows about its existence, actually this feature is not too well understood, and some are even rather afraid of it.
So I will try to explain moderately the knowledge and opportunities what is it why it should be used and as to make it.
Today I am glad to announce the course "Hacking PostgreSQL" from 16 occupations on which we will investigate together features of architecture of open DBMS and to make changes at the level of the source code. Will take a course in Moscow, on a site of the Postgres Professional company. The beginning of a course is planned for February, 2016. Lectures will begin right after the February pgconf.ru conference and will take place once a week in the evening. We will spread videos and materials of lectures in process of processing.
The course is built from personal experience developers of our company, materials from conferences, articles and thoughtful reading documentation and source codes. First of all it is addressed to beginning developers of a kernel of PostgreSQL. But it will be interesting also to DBA which sometimes should get into a code, and just by all not indifferent to architecture of big system, persons interested to learn "And how it works actually?"
1 year, 9 months ago
Hi! We let out IDE for work with databases.
One and a half years we did 0xDBE according to the program of early access (EAP). And here, we understood that it is time to put end under our work. We thank all who tried 0xDBE on the projects and wrote us — you very much helped. We will miss this name too.
DataGrip is universal IDE for work with MySQL, PostgreSQL, Oracle, SQL Server, Sybase, DB2, SQLite, HyperSQL, Apache Derby and H2.
Work with objects of a DB and code generation
DataGrip provides tools for work with database objects. If you create or change the table, add or change a column, an index, a key in already existing, use the graphic interface. Similar changes are followed by generation of the corresponding script — you can execute the made changes in base at once or copy the generated DDL request in the editor and work already directly with a code.
Machine learning is engaged in search of the hidden patterns in data. The growing growth of interest in this subject in IT community is connected with the exclusive results received thanks to it. Voice recognition and the scanned documents, search engines — all this is created with use of machine learning. In this article I will tell about the current project of our company: how to apply methods of machine learning to increase in performance of DBMS. The existing mechanism of the scheduler of PostgreSQL understands the first part of this article, in the second part it is told about opportunities of its improvement using machine learning.
1 year, 9 months agoThe subject of work with time marks in PostgreSQL is badly opened in Russian-language profile publications on the Internet and is a frequent source of problems in work of programmers. I bring to your attention transfer of material from Hubert Lubaczewski, the author of the popular foreign blog depesz.com. I hope, article will be useful to you!
From time to time in IRC or in mailing groups somebody asks questions which show deep misunderstanding (or a lack of understanding) of time stamps, especially those which consider time zones. As I already faced it earlier, allow me to tell that such timestamps as to work with them and what most widespread hitches you can face.
1 year, 9 months ago
In PostgreSQL 9.5 declarative safety of lines will appear. You can set rules for tables and make their execution automatic, for example, allowing the user of joe to see only lines which in the field of owner have a joe value.
It is the excellent tool and it had to appear for a long time. It it was not made in PostgreSQL 9.4, but made by means of automatically updated representations of security_barrier. They and the LEAKPROOF functions create the base on which safety of lines is constructed. You can use these components without support of declarative policy for achievement of safety of lines in 9.4.
Earlier I already discussed representation security_barrier. This post comprises examples of how there can be an information leakage from representation and as security_barrier of representation prevent such leaks. I will assume that you are familiar with the principles stated in the rest of article and I will repeatedly not stage demonstration of how there are information leakages from representations, etc.
1 year, 9 months ago
In general, relational database management systems were conceived as "one - the size - is suitable - all a solution for storage and data acquisition" for decades. But the growing need for scalability and new requirements of applications created new problems for traditional management systems of RSUBD, including some dissatisfaction with approach "one - the size - approaches - all" in a number of scalable applications.
The new generation of the lightweight, high-performance databases created to throw down a challenge to domination of relational databases was the answer to it.