Re: Bootstrap DATA is a pita

From: Mark Dilger <hornschnorter(at)gmail(dot)com>
To: Caleb Welton <cwelton(at)pivotal(dot)io>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bootstrap DATA is a pita
Date: 2015-12-12 04:43:12
Message-ID: B2B19B30-10F4-42F3-A7F5-F3DBE12174C0@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> On Dec 11, 2015, at 2:54 PM, Caleb Welton <cwelton(at)pivotal(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2015-12-12 04:49:22 Re: [PoC] Asynchronous execution again (which is not parallel)
Previous Message Tatsuo Ishii 2015-12-12 03:14:48 Re: Disabling an index temporarily