Re: WIP: a way forward on bootstrap data

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: John Naylor <jcnaylor(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: a way forward on bootstrap data
Date: 2018-01-15 13:36:04
Message-ID: 20180115133604.dv3x7qvxq4gsxgrp@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Tom Lane wrote:

> I had a thought about how to do that. It's clearly desirable that that
> sort of material remain in the manually-maintained pg_*.h files, because
> that's basically where you look to find out C-level details of what's
> in a particular catalog. However, that doesn't mean that that's where
> the compiler has to find it.
> [ elided explanation of pg_foo_d.h and pg_foo.h ]

Sounds good to me.

Álvaro Herrera
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marina Polyakova 2018-01-15 13:54:16 Re: [HACKERS] WIP Patch: Precalculate stable functions, infrastructure v1
Previous Message Aleksander Alekseev 2018-01-15 13:00:55 Re: new function for tsquery creartion