Postgresql Interview Questions
Postgresql Interview Questions
Postgresql is a widely used system for Object-Relational Database Management that is mainly used for large
web applications. Every year there are some vacancies, in big companies like Oracle, SQLite, Amazon web
services and such others, to fill up in this field. People with technical expertise in the computer can easily crack
the interview.
Here, we have listed few important and expected questions that may come up in your interview. With a little bit
of practice and hard work and thoroughness, the questions can be understood. Going through the questions, you
may find some questions that come up almost in every interview.
These predictable questions and answers will help you get through the interview without breaking a sweat.
1. Object-relational database
2. Support and Extensibility for SQL
3. flexible API and Database validation
4. MVCC and Procedural languages
5. WAL and Client server
Q2. What is the option that can be used in PostgreSQL to make transactions see rows
affected in previous parts of the transaction?
The SQL standard is defined by four levels of transaction isolation basically regarding three phenomena. The
three phenomenon must be prevented between concurrent transactions. The unwanted phenomena are:
Phantom read: A transaction that re-executes a query, returning a set of rows that satisfy a search
condition and then finds that the set of rows that have been satisfying the condition has changed due to
another recently-committed transaction.
Non-repeatable read: A transaction that re-reads the data that it has previously read and then finds that
data has already been modified by another transaction (that committed since the initial read).
Dirty read : A transaction when reads data that is written by a concurrent uncommitted transaction is the
dirty read.
MVCC or better known as Multi-version concurrency control is used to avoid unwanted locking of the
database. The time lag for the user is removed so that one can easily log into his database. All the transactions
are well- kept as a record. The time lag occurs when someone else is on the content.
It is not that hard as it seems. To get your statistics updated in PostgreSQL a special function called explicit
‘vacuum’ call is made. The method to do is to create Vacuum where the option of Analyze is used to update
statistics in Postgresql
VACUUM ANALYZE;
is the syntax.
Anywhere, functions are an important part because they help in executing the code on the server. Some of the
languages to program functions are PL/pgSQL, a native language of PostgreSQL, and other scripting languages
like Perl, Python, PHP, etc. statistical language named PL/R can also be used to increase the efficiency of the
functions.
There are new, different data-types supported by Postgresql. Following are those data-types:
Geometric primitives
Arbitrary precision numeric
XML
Arrays etc.
Users can also create their indexes and get them indexed.
Q7. Which are different types of database administration tools used in Postgresql?
There are the number of data administration tools, and they are
Phppgadmin
Psql
Pgadmin
Out of these, phppgadmin is the most popular one. Most of these tools are front-end administration tools and
web-based interfaces.
Q8. Do provide an explanation for pgadmin? (100% asked Postgresql Interview
Questions)
Pgadmin is a feature that is known to form a graphical front-end administration tool. This feature is available
under free software released under Artistic License. Pgadmin iii is the new database administration tool released
under artistic license.
Postgres or simply known as Postgresql in SQL world is one of the widely and popularly used for Object-
Relational Database Management System that is used mainly in large web applications. It is one of the open
source object-relational database system which also powerful. It provides additional and substantial power by
incorporating four basic concepts in such way that the user can extend the system without any problem. It
extends and uses the SQL language that is combined with various features to safely scale and store the intricate
data workloads.
The origin of PostgreSQL dates back to 1986 as part of the POSTGRES project at the University of California
at Berkeley and has more than 30 years of active development on the core platform. It runs on all the major
operating systems and has been ACID compliant since 2001. It also has add-on like PostGIS database extender.
In MAC OS Postgresql is default database. Michel Stonebraker is Father of Postgresql who has started Post
Ingres project for supporting Contemporary Database systems.PostgreSQL’s developers pronounce PostgreSQL
as It is abbreviated as Postgres because of ubiquitous support for the SQL Standard among most relational
databases.PostgreSQL, originally called Postgres, was created at UCB by a computer science professor named
Michael Stonebraker, who went on to become the CTO of Informix Corporation.
Stonebraker started Postgres in 1986 as a followup project to its predecessor, Ingres, now owned by Computer
Associates. The name Postgres thus plays off of its predecessor (as in “after Ingres”). Ingres, developed from
1977 to 1985, had been an exercise in creating a database system according to classic RDBMS theory. Postgres,
developed in 1986-1994, was a project meant to break new ground in database concepts such as exploration of
“object-relational” technologies. An enterprise-class database, PostgreSQL boasts sophisticated features such as
Multi-Version Concurrency Control (MVCC), point in time recovery, tablespaces, asynchronous replication,
nested transactions (savepoints), online/hot backups, a sophisticated query planner/optimizer, and write ahead
logging for fault tolerance.
Stable
Reliable
Extensible
Easy to learn
Open source
Designed for High Volume Environments
Cross Platform
Better Support
Flexible
Multi-version concurrency control or MVCC is used to avoid unnecessary locking of the database. This
removes the time lag for the user to log into his database. This feature or time lag occurs when someone else is
accessing the content. All the transactions are kept as a record.
A sequence of characters bound by single quotes is contained by string constants. This feature is used when one
needs to insert a character or to pass a character to database objects. PostgreSQL allows the usage of single
quotes but embedded by a C style backslash. A string constant is a sequence of characters bound together by
single quotes instead of double quotes, which is generally the case with string type variables. This feature is
mostly used when a character is being inserted or when a character needs to be passed to database objects. This
feature is exceptionally important while parsing data. PostgreSQL lets a user use single quotes only when it is
embedded by the specific C-style backslash.
CTIDs is a field, which exists in every PostgreSQL table and is known to identify specific physical rows
according to their block and offset positions within a particular table. They are used by index entries to point to
physical rows. It is unique for each record in the table and easily denotes the location of a tuple. A logical row’s
CTID changes when it is updated, so the CTID cannot be used as a long-term row identifier. However, it is
sometimes useful to identify a row within a transaction when no competing update is expected.
WAL or write-ahead logging is a standard method to ensure data integrity. It is a protocol or the correct rule to
write both actions and changes into a transaction log. This feature is known to increase the reliability of the
database by logging changes before any changes or updating to the database. This provides the log of the
database in case of a database crash. This helps to start the work from the point it was discontinued.
The command enable-debug is used to enable the compilation of all the applications and libraries. The execution
of this procedure usually impedes the system, but it also amplifies the binary file size. Debugging symbols
which are present generally assist the developers for spotting the bugs and other problems which may arise
associated with their script.
Tokens are the building blocks of any source code. They are known to comprise many of the special character
symbols. These can be regarded as constants, quoted identifiers, other identifiers, and keywords. Tokens which
are keywords consist of pre-defined SQL commands and meanings. Identifiers are used to represent variable
names like columns, tables, etc.
Before you can have access to the database, you must be able to start the database server. The server program of
the database is called Postgres. The Postgres program must know where to find the data it is supposed to use.
This is done with the -D option. Thus, the simplest way to start the server is:
1. /usr/local/etc/rc.d/010.pgsql.sh start
2. /usr/local/etc/rc.d/PostgreSQL start
During the process of updating the project, one can never be certain what features will go in and which ones
won’t make the cut. The project has precise and stringent standards for quality, and some patches may or may
not match them before the set deadline. Currently, the 9.1 version is working on some important features which
include JSON support, synchronous replication, nearest-neighbor geographic searches, collations at the column
level, SQL/MED external data connections, security labels as well as index-only access. However, this list has a
high chance of changing completely by the time Postgre 9.1 is released.
The expression ‘NoSQL’ encompasses a wide collection of implementations which are part of the non-relational
database. This includes tiny embedded databases such as TokyoCabinet, massive bunched data processing
platforms such as Hadoop and everything in between. In short, it’s practically impossible to comment on the
range comprised by NoSQL as a typical class.
Choosing between the non-relational and relational databases is also quite commonly debated as both have
existed alongside each other for over forty years. In fact, users should opt for the features, community support
and implementation of the database according to their current application needs. Additionally, use of multiple
various databases for sizeable projects is becoming more of a norm than a trend. Moreover, the users of
PostgreSQL are no exception.