A brief description of installation and config of the PGMon project. As this project has two separate and more or less independent parts - a part responsible for data collection and a web interface used to display collected data - it's necessary to install and configure both of these parts.
This article contains brief description of database structure used for the PGMon project - tables, their structure, etc.
Installation and configuration of the OpenStats library consists of several quite simple steps - let's investigate them a little bit.
If you're interested in OpenStats project and you have installed it (see installation and configuration), there is nothing easier than trying to log several sessions, actions or parameters ;-)
Goal of this article is to describe the database structure used for OpenStats project in a nutshell (but with enough details). It contains description of individual tables and their columns, but an explanation of some seemingly illogical solutions.
This article extends an article about reasons to store user files in a database and not in a filesystem, and describes several ways how to do that in PostgreSQL. There are BLOBs, BYTEA columns, custom solutions, and all of them have advantages / disadvantages, so let's investigate them.
Imagine you are working on a web application that requires storing of files (e.g. a photo gallery). And there comes a question "Should I store the files in a database, or directly on the filesystem?" Maybe you've asked this question on a discussion forum / mailing list and I guess the answer you've received was something like "It's much more efficient to store files outside the database." Well, I'll try to explain why I prefer storing files in a database. This article is based on a discussion I've had with James Lewis, after I posted a question to pg-php mailing list.
