Tanto quienes emplean DB2 para crear archivos como quienes se manejan a través de DDS, utilizan los valores por omisión para crear archivos físicos. En los valores por omisión el sistema operativo establece que el archivo va a tener un solo miembro.
Los archivos lógicos que son creados posteriormente, “apuntan” a ese miembro. Read more »

Cumulative Update 7 contains hotfixes for the Microsoft SQL Server 2008 R2 issues that have been fixed since the release of SQL Server 2008 R2. Read more »

It’s not always necessary to create new spatial data, especially if your data comes from a surveyor office . But how can we automatically add the geometry of a Shape to our database (Postgresql/PostGIS), without adding all different row types, which are delivered by the *.dbf?
Before we start, check out some additional requirements:
Read more »

Hace varios meses que no dictaba una charlita y pues sucedió que los amigos me invitaron a las Jornadas 2011 que siempre organizan en la UTP, el tema que escogí es del que siempre me gusta más hablar, PostgreSQL, y esta vez como ya en mis últimas charlas me adentro en el funcionamiento interno de la base de datos para transmitir como moraleja: “hacer estás cosas no es difícil”, aquí les dejo mi expo y algunas fotitos que tomé el sábado. Read more »

I recently covered the internals of a row in PostgreSQL, but that was just the storage piece. I got more curious and decided that I would look into what happens when a row gets updated. There are a lot of complexities to data, after all, and it’s nice to know how our database is going to be affected by updates.
Getting Set Up
I started by using the customer table from the pagila sample database. Rather than come up with a set of sample data, I figured it would be easy to work within an existing set of data.
The first trick was to find a customer to update. Since the goal is to look at an existing row, update it, and then see what happens to the row, we’ll need to be able to locate the row again. This is actually pretty easy to do. The first thing I did was retrieve the ctid along with the rest of the data in the row. I did this by running: Read more »

The PostgreSQL Global Development Group today released bug fix updates for all active branches of the PostgreSQL database system, including versions 9.0.4, 8.4.8, 8.3.15 and 8.2.21. This update contains a critical fix to the pg_upgrade utility which prevents significant downtime issues. Do not use pg_upgrade without installing this update first.
The issue with pg_upgrade and the fix are detailed on the PostgreSQL wiki: http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix. Users who have already used pg_upgrade should run the database repair script given on that page on their databases as soon as possible.
In addition to pg_upgrade, the following fixes are included in the update. Not all fixes affect all versions. Read more »