Re: varchar vs Text & TOAST

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Ow Mun Heng <Ow(dot)Mun(dot)Heng(at)wdc(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: varchar vs Text & TOAST
Date: 2008-09-08 04:50:25
Message-ID: 48C4AF11.1000201@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ow Mun Heng wrote:

> Anyhow, searching the archives (in my mail client - no internet at the
> moment), I see references that when I use TEXT, I will create TOAST
> tables which will have them lie _outside_ of my main data table.

The same is true of varchar, and quite a few other data types. There's
more detail about which data types are and are not toastable, and how,
in the PostgreSQL documentation.

> oh.. i didn't like the TOAST tables cos it's created
> _not_ in my usual raidspace, but in my OS drive

My understanding was that toast tables were by default created in the
same tablespace as their owning tables, but I could be wrong there.
Again, the documentation will probably tell you for sure.

Note that if you are relying on RAID to protect your database but are
not storing pg_clog, pg_xlog, etc on your RAID volume then you are
experiencing a false sense of security. You must make sure to protect
the whole cluster, including transaction logs etc. Similarly, if you're
using volume-level snapshots rather than pg_dump or Pg's host cluster
copy support to take backups you need to be able to get a consistent
snapshot across ALL of the cluster.

If you want the database to live on the RAID volume, consider moving the
whole cluster there.

--
Craig Ringer

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ivan Zolotukhin 2008-09-08 09:46:01 8.3 on FreeBSD 6.3, sudden performance degradations
Previous Message Justin Graf 2008-09-08 04:39:24 Re: Very weird problem of "order by" in postgresql