| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Mark Dilger <hornschnorter(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Caleb Welton <cwelton(at)pivotal(dot)io>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bootstrap DATA is a pita |
| Date: | 2015-12-12 00:44:03 |
| Message-ID: | 4981.1449881043@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2015-12-11 19:26:38 -0500, Tom Lane wrote:
>> I believe it's soluble, but it's going to take something more like
>> loading up all the data at once and then doing lookups as we write
>> out the .bki entries for each catalog. Fortunately, the volume of
>> bootstrap data is small enough that that won't be a problem on any
>> machine capable of running modern Postgres ...
> I think that's exactly the right approach. Just building a few perl
> hashes worked well enough, in my prototype of that.
Right. I would draw Mark's attention to src/backend/catalog/Catalog.pm
and the things that use that. Presumably all that would have be
rewritten, but the existing code would be a useful starting point
perhaps.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2015-12-12 01:22:38 | Re: Rework the way multixact truncations work |
| Previous Message | Andres Freund | 2015-12-12 00:36:45 | Re: Bootstrap DATA is a pita |