Re: pg_dumping large objects

From: Erik Jones <erik(at)myemma(dot)com>
To: Morris Goldstein <morris(dot)x(dot)goldstein(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dumping large objects
Date: 2007-09-24 17:57:10
Message-ID: 33F5763F-172F-47A8-BEB3-0036EBAB002B@myemma.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sep 24, 2007, at 12:48 PM, Morris Goldstein wrote:

> pg_dump --help says:
>
> -b, --blobs include large objects in dump
>
> What is the definition of "large object"? Is it a certain set of types
> (e.g. text)? Long values stored in these types? What qualifies as
> long? In general, how can I tell if I need the -b flag (postgres 7.4).

The short answer is that if you don't know, you don't need it. The
longer answer is that large objects are a specialized data type that
allows you store values/datum up to 2GB in size whereas the normal,
behind the scenes TOAST mechanism only handles up to 1GB values. So,
they are not specialized versions of any other data type, they are
their own, separate data type.

http://www.postgresql.org/docs/8.2/interactive/largeobjects.html

Erik Jones

Software Developer | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)

Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Vivek Khera 2007-09-24 18:03:58 Re: For index bloat: VACUUM ANALYZE vs REINDEX/CLUSTER
Previous Message Morris Goldstein 2007-09-24 17:48:52 pg_dumping large objects