Bruce Momjian wrote:
> > Then the answer is "don't do that." Surely it's far saner to run
> > configure --prefix=/path/to/temploc and then go from there. Disturbing a
> > running postmaster for this purpose is crazy. BTW, for years I've used a
> > gadget to set up every piece of development work
Andrew Dunstan wrote:
>
>
> On 06/09/2011 11:28 PM, Bruce Momjian wrote:
> > Andrew Dunstan wrote:
> >>
> >>
> >>
> >> On 06/09/2011 08:51 PM, Bruce Momjian wrote:
> >>> Mention "pg_ctl stop" in pgindent README instructions.
> >>>
> >> This change make no sense at all. Why would you be running 'p
On 06/09/2011 11:28 PM, Bruce Momjian wrote:
Andrew Dunstan wrote:
On 06/09/2011 08:51 PM, Bruce Momjian wrote:
Mention "pg_ctl stop" in pgindent README instructions.
This change make no sense at all. Why would you be running 'pg_ctl stop'
when there is nothing to suggest that there's a
Andrew Dunstan wrote:
>
>
>
>
> On 06/09/2011 08:51 PM, Bruce Momjian wrote:
> > Mention "pg_ctl stop" in pgindent README instructions.
> >
>
> This change make no sense at all. Why would you be running 'pg_ctl stop'
> when there is nothing to suggest that there's a postgres running. And
> e
On 06/09/2011 08:51 PM, Bruce Momjian wrote:
Mention "pg_ctl stop" in pgindent README instructions.
This change make no sense at all. Why would you be running 'pg_ctl stop'
when there is nothing to suggest that there's a postgres running. And
even if there is there's not the slightest re
Mention "pg_ctl stop" in pgindent README instructions.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/bb8f0c4b4863d697264cc6f295f50627b15a6608
Modified Files
--
src/tools/pgindent/README |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
--
Sen
