Tom Lane wrote:
> Bruce Momjian writes:
> > I think it is hard to argue that such a user-visible flag is
> > reasonable, even if it helps backend developers avoid some keystrokes.
>
> > I think flags used only by backend developers should be things that can
> > _only_ be done with flags.
>
> Hu
Bruce Momjian writes:
> I think it is hard to argue that such a user-visible flag is
> reasonable, even if it helps backend developers avoid some keystrokes.
> I think flags used only by backend developers should be things that can
> _only_ be done with flags.
Huh? By that argument, we should
Tom Lane wrote:
> Heikki Linnakangas writes:
> > While looking at Shigeru Hanada's foreign join pushdown patch, I noticed
> > a command line option that I didn't know to exist:
>
> > $ postgres --help
> > ...
> > Developer options:
> >-f s|i|n|m|hforbid use of some plan types
>
> Hmm, I
Heikki Linnakangas writes:
> While looking at Shigeru Hanada's foreign join pushdown patch, I noticed
> a command line option that I didn't know to exist:
> $ postgres --help
> ...
> Developer options:
>-f s|i|n|m|hforbid use of some plan types
Hmm, I thought I'd fixed that help message
Heikki,
On 17.11.2011 10:19, Heikki Linnakangas wrote:
$ postgres --help
...
Developer options:
-f s|i|n|m|hforbid use of some plan types
That doesn't include all the options we support, the documentation
lists: s|i|o|b|t|n|m|h. These are aliases for enable_* planner
options, e.g -fs is
Excerpts from Robert Haas's message of jue nov 17 10:14:21 -0300 2011:
> On Thu, Nov 17, 2011 at 4:19 AM, Heikki Linnakangas
> wrote:
> > While looking at Shigeru Hanada's foreign join pushdown patch, I noticed a
> > command line option that I didn't know to exist:
> >
> > $ postgres --help
> > .
On Thu, Nov 17, 2011 at 4:19 AM, Heikki Linnakangas
wrote:
> While looking at Shigeru Hanada's foreign join pushdown patch, I noticed a
> command line option that I didn't know to exist:
>
> $ postgres --help
> ...
> Developer options:
> -f s|i|n|m|h forbid use of some plan types
>
> That does