Re: pg_dump, BLOBs and single-table dumps - RFC

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: PostgreSQL Hackers <pgsql-hackers(at)hub(dot)org>, Denis Perchine <dyp(at)perchine(dot)com>
Subject: Re: pg_dump, BLOBs and single-table dumps - RFC
Date: 2000-10-08 04:11:28
Message-ID: 200010080411.AAA03017@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Also, scanning through the backup file for BLOBs used in the table to be
> restored will be slow, to say the least. It can be done in one pass by
> building an indexed temporary table with all OID fields from the target
> table, but it is definitely getting messy. Especially since Jan was talking
> about a decent BLOB implementation RSN.
>
> My inclination at this stage is to disallow --blobs when dumping or
> restoring a single table, but I would be interested in hearing from anybody
> with a better solution.

I agree.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-10-08 04:25:29 Re: Re: Alpha spinlock
Previous Message Bruce Momjian 2000-10-08 04:02:57 Re: failed to compile a C++ SPI function