Items in Category: Database


« Older Posts


PG Phriday: 10 Ways to Ruin Performance: Sex Offenders

July 24th, 2015 | Published in Database, Tech Talk | 1 Comment


We’re finally at the end of the 10-part PGDB (PostgreSQL) performance series I use to initiate new developers into the database world. To that end, we’re going to discuss something that affects everyone at one point or another: index criteria. Or to put it another way:

Why isn’t the database using an index?


Tags: , , , ,

PG Phriday: 10 Ways to Ruin Performance: Indexing the World

July 17th, 2015 | Published in Database, Tech Talk | No Comments


An easy way to give PGDB (PostgreSQL) a performance boost is to judiciously use indexes based on queries observed in the system. For most situations, this is as simple as indexing columns that are referenced frequently in WHERE clauses. PGDB is one of the few database engines that takes this idea even further with partial indexes. Unfortunately as a consequence of insufficient exposure, most DBAs and users are unfamiliar with this extremely powerful functionality.


Tags: , , , ,

PG Phriday: 10 Ways to Ruin Performance: MAXimized Value

July 10th, 2015 | Published in Database, Tech Talk | No Comments


I apologize for putting this series on a short hiatus last week for the 4th of July. But worry not, for this week is something special for all the developers out there! I’m going to try to make your life easier for a change. Screw the database!

As a PGDB (PostgreSQL) DBA, it’s easy to get tied up in performance hints, obscure syntax, and mangled queries, but it’s really all about the people. These men and women who hit our databases all day long in an attempt to hit insane deadlines often stare at the screen in defeat, trying to get something to work because they’re afraid to ask for help. I know, because I used to be one of them in my bygone developer days.


Tags: , , , ,

PG Phriday: 10 Ways to Ruin Performance: In The Loop

June 26th, 2015 | Published in Database, Tech Talk | 1 Comment


As a database, PGDB (PostgreSQL) is fairly standard in its use of SQL. Developers of all colors however, might have trouble switching gears and thinking in set operations, since so many language constructs focus on conditionals and looping. Last week in the performance pitfalls series, [intlink id='pg-phriday-10-ways-to-ruin-performance-functionally-bankrupt']we discussed[/intlink] a bit of Set Theory, and how ignorance of its implications can be disastrous. But what about the more mundane?

What happens, for instance, when we treat a database like a programming language?


Tags: , , , ,

PGCon 2015 Unconference: A Community

June 23rd, 2015 | Published in Database, Tech Talk | No Comments


Well, I’ve returned from PGCon 2015 in Canada, and after a couple days to decompress, it’s time to share. I wrote about the [intlink id='pgcon-2014-unconference-a-community']PGCon 2014 unconference[/intlink] after returning to Chicago last year, so I felt it was only fitting that I start there. I feel as strongly now as I did a year ago, that directly interacting with the PostgreSQL maintainers at this level helps the community thrive. Even though PGCon is generally a more developer-focused conference, being able to brainstorm with the bigwigs, even if nothing comes of it, means the ideas have been given a fair shake.


Tags: , , , ,

« Older Posts