| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Subject: | Re: Table description in the data file (Re: pg_rawdump) |
| Date: | 2015-02-04 05:48:03 |
| Message-ID: | 54D1B293.604@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/3/15 1:43 AM, Stephen R. van den Berg wrote:
> In relation to the talk and discussions at FOSDEM regarding
> helping data recovery, I searched the archives for the
> old thread after I performed my last recovery; for reference:
>
> http://www.postgresql.org/message-id/20101019201223.GA15684@cuci.nl
>
> I haven't checked yet if the proposed space there is still
> available in the current disk format, but it might serve as
> a starter and reminder to get the discussion going once more.
Rather than trying to wedge this into a heap page, ISTM it'd be better
to use a fork. Presumably if you're storing regular tuples that have the
essential data from pg_class, pg_attribute (and maybe pg_type).
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-02-04 05:55:04 | Re: Fetch zero result rows when executing a query? |
| Previous Message | Tom Lane | 2015-02-04 05:44:37 | Re: Proposal : REINDEX xxx VERBOSE |