Re: Bootstrap DATA is a pita - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: Bootstrap DATA is a pita
Date
Msg-id B2B19B30-10F4-42F3-A7F5-F3DBE12174C0@gmail.com
Whole thread Raw
In response to Re: Bootstrap DATA is a pita  (Caleb Welton <cwelton@pivotal.io>)
Responses Re: Bootstrap DATA is a pita  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

On Dec 11, 2015, at 2:54 PM, Caleb Welton <cwelton@pivotal.io> wrote:

The current semantic level is pretty low level, somewhat cumbersome, and requires filling in values that most of the time the system has a pretty good idea how to fill in default values.

Compare:

CREATE FUNCTION lo_export(oid, text) RETURNS integer LANGUAGE internal STRICT AS 'lo_export' WITH (OID=765);  

DATA(insert OID = 765 (  lo_export   PGNSP PGUID 12 1 0 0 0 f f f f t f v u 2 0 23 "26 25" _null_ _null_ _null_ _null_ _null_ lo_export _null_ _null_ _null_ ));

I would like to hear more about this idea.  Are you proposing that we use something
like the above CREATE FUNCTION format to express what is currently being expressed
with DATA statements?  That is an interesting idea, though I don't know what exactly
that would look like.  If you want to forward this idea, I'd be eager to hear your thoughts.
If not, I'll try to make progress with my idea of tab delimited files and such (or really,
Alvaro's idea of csv files that I only slightly corrupted).

mark

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: Disabling an index temporarily
Next
From: Amit Kapila
Date:
Subject: Re: [PoC] Asynchronous execution again (which is not parallel)