CYBERTEC PostgreSQL Logo

Category: Performance

Get the Newest PostgreSQL Info, Tips & Tricks
Here you can find all blog posts about the Category: Performance. You can go back to all blog posts or take a look into our other categories & tags.

The power of response times and execution time

by Hans-Jürgen Schönig | 04.2014
The goal of the PostgreSQL optimizer is to provide a plan which executes as fast as possible & returns all the data as rapidly as possible.

wal_level: What is the difference?

by Hans-Jürgen Schönig | 03.2014
PostgreSQL replication requires changing the wal_level from “minimal” to “hot_standby”. What er the impacts? Read out more.

Logging - the hidden speedbrakes

by Hans-Jürgen Schönig | 03.2014
When it comes to performance, people tend to forget some basic topics entirely. One of those topics is the impact of writing log files.

max_connections - Performance impacts

by Hans-Jürgen Schönig | 03.2014
Setting max_connections to an insanely high value is not good for performance. I tried it, to see what impact it has in PostgreSQL.

Adjusting maintenance_work_mem

by Hans-Jürgen Schönig | 02.2014
After testing shared_buffers recently, I decided to do a little more testing on our new office desktop PC (8 core […]

PostgreSQL 9.3 - Shared Buffers Performance (1)

by Hans-Jürgen Schönig | 02.2014
A lot has been said about PostgreSQL shared buffers and performance. As my new desktop box has arrived this week […]

Security barriers: Cheating on the planner

by Hans-Jürgen Schönig | 12.2013
UPDATED Aug. 2023 - How a security barrier can theoretically be used to speed up PostgreSQL queries and to see how PG works under the hood.

Detecting table bloat in PostgreSQL

by Hans-Jürgen Schönig | 08.2013
If your PostgreSQL database is badly structured, you might face some table bloat. Figure out if a table is bloated or not.

Functions: The most widely ignored performance tweak

by Hans-Jürgen Schönig | 05.2013
A PostgreSQL function performance can be marked as follows: VOLATILE, STABLE, IMMUTABLE or [NOT] LEAKPROOF. Undestand why.

pgbouncer: Proving the point

by Hans-Jürgen Schönig | 05.2013
pgbouncer: Opening and closing a database connection over and over again is not free, but overhead worth thinking about.
1 … 14 15 16 17
CYBERTEC Logo white
CYBERTEC PostgreSQL International GmbH
Römerstraße 19
2752 Wöllersdorf
Austria

+43 (0) 2622 93022-0
office@cybertec.at

STAY TUNED WITH OUR NEWSLETTER
Get the newest PostgreSQL Info & Tools


    This site is protected by reCAPTCHA and the Google Privacy Policy & Terms of Service apply.

    ©
    2024
    CYBERTEC PostgreSQL International GmbH
    phone-handsetmagnifiercrosscross-circle
    linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram