| From: | Mark Dilger <hornschnorter(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, pgsql-hackers(at)postgresql(dot)org, Caleb Welton <cwelton(at)pivotal(dot)io>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Subject: | Re: Using a single standalone-backend run in initdb (was Re: Bootstrap DATA is a pita) |
| Date: | 2015-12-13 16:34:19 |
| Message-ID: | 7093B73D-B0BE-4DAC-A298-8C36F09F25EE@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Dec 12, 2015, at 9:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Mark Dilger <hornschnorter(at)gmail(dot)com> writes:
>>> On Dec 12, 2015, at 3:42 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> ... In general, though, I'd rather not try to
>>> teach InteractiveBackend() such a large amount about SQL syntax.
>
>> I use CREATE RULE within startup files in the fork that I maintain. I have
>> lots of them, totaling perhaps 50k lines of rule code. I don't think any of that
>> code would have a problem with the double-newline separation you propose,
>> which seems a more elegant solution to me.
>
> Yeah? Just for proof-of-concept, could you run your startup files with
> the postgres.c patch as proposed, and see whether you get any failures?
Given all the changes I've made to initdb.c in my fork, that patch
of yours doesn't apply.
mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-12-13 17:05:30 | Re: Using a single standalone-backend run in initdb (was Re: Bootstrap DATA is a pita) |
| Previous Message | Magnus Hagander | 2015-12-13 16:01:58 | Re: pg_stat_replication log positions vs base backups |