First steps with pgbouncer, how to set and run it

2013-07-09 03:00:27 +0000

pgbouncer is a connection pooling utility that can be plugged on top of a PostgreSQL server. It can be used to limit the maximum number of connections on server side by managing a pool of idle connections that can be used by any applications. Something particularly good about pgbouncer is that it offers the same level of transparency as a normal PostgreSQL server when an application connects to it. Also, the project is mature for years, its code is stable and is used in many production environments.

Postgres 9.3 feature highlight - Data Checksums

2013-07-02 07:54:18 +0000

Data checksums is a new feature introduced in PostgreSQL 9.3, adding a new level of checksum to protect data from disk and I/O corruption, controlled directly by the database server. This has been introduced by the commit below.

Postgres devel - some psql tricks

2013-06-26 00:33:20 +0000

psql, the command client delivered with postgres core, has many options and is in this way highly customizable. For example, you can use a ~/.psqlrc file to upload automatically some customized settings when launching psql. Here are some general tips to be aware off as a common user.

Postgres 9.3 feature highlight - new verbose error fields

2013-05-22 18:28:32 +0000

PostgreSQL is already pretty useful for application developers when returning to client error messages by providing a certain level of details with multiple distinct fields like the position of the code where the error occurred. However this was lacking with the database object names, forcing the client application to deparse the error string returned by server, generally with field ‘M’, to get more details about the objects that have been involved in the errors. This functionality has been added in PostgreSQL 9.3 thanks to this commit.

Postgres 9.3 feature highlight - new flavors of IF EXISTS and IF NOT EXISTS

2013-05-15 11:51:07 +0000

IF EXISTS and IF NOT EXISTS are clauses allowing to return a notice message instead of an error if a DDL query running on a given object already exists or not depending on the DDL action done. If a given query tries to create an object when IF NOT EXISTS is specified, a notice message is returned to client if the object has already been created and nothing is done on server side. If the object is altered or dropped when IF EXISTS is used, a notice message is returned back to client if the object does not exist and nothing is done.

« Prev 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 Next »

Michael Paquier - PostgreSQL committer

First steps with pgbouncer, how to set and run it

Postgres 9.3 feature highlight - Data Checksums

Postgres devel - some psql tricks

Postgres 9.3 feature highlight - new verbose error fields

Postgres 9.3 feature highlight - new flavors of IF EXISTS and IF NOT EXISTS

Search

Social

RSS Feeds

Sponsor