Re: Using a single standalone-backend run in initdb (was Re: Bootstrap DATA is a pita) - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: Using a single standalone-backend run in initdb (was Re: Bootstrap DATA is a pita)
Date
Msg-id 7093B73D-B0BE-4DAC-A298-8C36F09F25EE@gmail.com
Whole thread Raw
In response to Re: Using a single standalone-backend run in initdb (was Re: Bootstrap DATA is a pita)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On Dec 12, 2015, at 9:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Mark Dilger <hornschnorter@gmail.com> writes:
>>> On Dec 12, 2015, at 3:42 PM, Tom Lane <tgl@sss.pgh.pa.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


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: pg_stat_replication log positions vs base backups
Next
From: Tom Lane
Date:
Subject: Re: Using a single standalone-backend run in initdb (was Re: Bootstrap DATA is a pita)