Questions about large objects and the WAL

From: Karen Ploski <ploskikl(at)yahoo(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Questions about large objects and the WAL
Date: 2006-02-28 22:14:13
Message-ID: 20060228221413.70711.qmail@web50505.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I'm trying to understand how large objects relate to
the write-ahead log. I've read the following sections
in the 8.1 user guide:

Chapter 26 Reliability and the Write-Ahead Log
Chapter 29 Large Objects
Section 42.21 pg_lageobject

I have some naive questions

(1)When a large object is updated, how much of the
large object is placed in the WAL buffers in shared
memory by LogInsert?
(a) None
(b) Just the page (or pages) in pg_largeobject that
changed, or
(c) the entire large object?

(2) Are the WAL buffer(s) that contain part (or all)
of the large object written to the log file, on
permanent storage?

(3) Section E.1.3.12. pg_dump Changes in the 8.1
documentation describes a change to pg_dump:

• Allow pg_dump to dump large objects even in text
mode (Tom)
With this change, large objects are now always dumped;
the former -b switch is a no-op.

Does pg_dump take the large objects from the shared
WAL buffers, or the log file (or both)?

I have similar questions about TOAST fields. I assume
that TOAST fields aren't "stored" in pg_largeobject,
they are not "broken into pages" like large objects.
Apart from that,

(4) are TOAST fields written to the log file, on
permanent storage?
(5) does pg_dump dump TOAST fields (8.1 and later)?

Thank you!
Karen

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Responses

Browse pgsql-general by date

  From Date Subject
Next Message CG 2006-02-28 23:00:32 Re: ltree + gist index performance degrades significantly over a night
Previous Message flood 2006-02-28 21:54:45 Full Text Indexing and Syntax