| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:36:45 |
| Message-ID: | 20151212003645.GQ14789@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
If additionally a few more plain oid fields are converted into reg*
types, the source data fields are easier to understand and the catalogs
get much nicer to query...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-12-12 00:44:03 | Re: Bootstrap DATA is a pita |
| Previous Message | Tom Lane | 2015-12-12 00:34:06 | Re: Fwd: [GENERAL] pgxs/config/missing is... missing |