On Thu, Jan 31, 2019 at 05:09:09PM +0100, Michael Banck wrote:
> Sorry, I didn't look at it during that (November) commitfest cause it
> was submitted late, and then forgot about it.
>
> I think the changes are fine and I've marked it Ready for Committer.
Agreed, so committed.
--
Michael
signat
Hi,
On Sat, Nov 03, 2018 at 09:56:46PM +0100, Andreas 'ads' Scherbaum wrote:
> >That's indeed one replacement too much.
> >
> >The attached patch is fixing this.
> >
> >Thank you for the review!
> >
>
> Submitted this to the Commitfest, and took the liberty to add you as a
> reviewer.
Sorry, I d
I used the updated instructions from pg_ctl.diff to install from source.
Worked well for me, new version is more consistent.
On 30.10.18 14:52, Andreas 'ads' Scherbaum wrote:
On 30.10.18 09:04, Michael Banck wrote:
Hi,
On Tue, Oct 30, 2018 at 12:08:49AM +0100, Andreas 'ads' Scherbaum wrote:
The installation instructions (short version) are not consistent
with the
"initdb" output. The first one still uses "postgres
On 30.10.18 09:04, Michael Banck wrote:
Hi,
On Tue, Oct 30, 2018 at 12:08:49AM +0100, Andreas 'ads' Scherbaum wrote:
The installation instructions (short version) are not consistent with the
"initdb" output. The first one still uses "postgres -D", even mentions
"check initdb output", but "initd
Hi,
On Tue, Oct 30, 2018 at 12:08:49AM +0100, Andreas 'ads' Scherbaum wrote:
> The installation instructions (short version) are not consistent with the
> "initdb" output. The first one still uses "postgres -D", even mentions
> "check initdb output", but "initdb" emits "pg_ctl" commands.
>
> The
