As I became responsible for recording and processing videos from regular CZJUG meetings, I had to learn how to perform basic video processing in Linux - years ago I did this on Windows in Adobe Premiere, so I have been looking fro a similarly comfortable and flexible solution. I guess you are trying to solve about the same problem, so lets review my solution based on ffmpeg and kdenlive.
Installing Oracle 11g (R2) on an unsupported distribution (currently there are three supported ones - Oracle Enterprise Linux, Red Hat and SuSe) may be a bit of a problem - especially if the distribution is "progressive" i.e. contains fresh versions of different tools (compiler, libraries) and is not based on RPM packages. And both of these are true for Gentoo, so lets see what problems may occur during the installation (and how to solve them).
If you plan to partition a continually growing table to parts of a limited size, you'll have to find a suitable way to create new partitions. It's not advisable to do that manually (at least on a production system), it's much better to do that automatically. Lets see several possible solutions ...
In PostgreSQL there are two different ways to perform partitioning - using rules and using triggers. One of the usual reasons why a partitioningu is used, is a performance, so lets analyze differences between these two ways regarding performance.
In contrast to the previous articles focused on technology, this one is a short reasoning about hints in Oracle. My approach to hints is somehow ambiguous - from time to time I do admit hints may be useful, but most of the time I just hate them ...
Partitioning may be used as a quite elegant solution of a wide variety of problems - distributing the table to multiple drives (if you don't want to use a traditional RAID), effective removal of archive data (without DELETE), etc. It may be automatically realized using triggers or rules. Lets see a puzzler related to partitioning realized with rules.
If you have ever engaged in performance tuning in one of the newer Oracle versions, maybe you have met the legendary statspack (see Oracle Statspack Survival Guide), or its successor Automatic Workload Repository (AWR), whose main principle lies in creating "snapshots" of important internal values (number of queries, transactions, disk reads, cache reads, etc) and consequent analysis of differences between snapshots. It is not widely known that there is a similar tool for PostgreSQL called pgstatspack, which references to Statspack even by its name - it is based on the very same principle (analysis of snapshot differences), and although it is more simple, it may provide invaluable services when tuning performance.
About a year ago I've bought an Eee PC 1000H netbook made by Asus - right from the beginning I've been using it with Gentoo which is my favourite distribution, with a KDE 3.5. There were some issues but most of the time it ran just fine. But as I'm a notorious breaker and I ignore most of the messages produced by portage, the netbook reached a point of no return - there was no other way than a fresh install - this time with a KDE 4.3 environment.
I forwarn you this is not an installation guide - after all we have a great Gentoo Handbook for that. It's rather a collection of useful and interesting information specific for the 1000H (and maybe other netbooks too), eg. kernel configuration, use flags, issues I've ran into, etc.
When developing applications, every now and then it's necessary to test application's behaviour in case the database server suddenly "dies." In the PostgreSQL mailing list there was an interesting thread, describing several interesting ways how to simulate this (from very elegant ones to quite brutal ones). Let's see various ways of killing PostgreSQL ...
It is said that "A road to hell is paved with good intentions," and it's true even for SQL queries. A lot of problems is caused by developers who strive to optimize the database, frequently without necessary knowledge of the internals.
