From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: unix_socket_directory |
Date: | 2004-12-20 18:28:33 |
Message-ID: | 1103567313.22049.148.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 2004-12-17 at 22:10, Bruce Momjian wrote:
> Scott Marlowe wrote:
> > On Fri, 2004-12-17 at 16:18, Tom Lane wrote:
> > > Scott Marlowe <smarlowe(at)g2switchworks(dot)com> writes:
> > > >> Not sure, but I think you need quotes:
> > > >> unix_socket_directory = '/home/pgmaster/tmp'
> > >
> > > > Wow, that was way too simple.
> > >
> > > > So, is there a reason some things in the postgresql.conf file need '
> > > > marks around them and other things, like client_min_messages don't?
> > >
> > > I think the rule is anything but a number or identifier needs quotes,
> > > but I'm too lazy to go check.
> >
> > That's what I figured, and I too, am too lazy to go look.
>
> Some GUC parameters are integers, boolean, or floats, that don't need
> quotes, and some are strings that do.
What confused me was the constants that don't need quotes (like
client_min_messages) and can be set to many different string constants.
But they're all still constants, not vars.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-12-20 18:37:33 | Re: unix_socket_directory |
Previous Message | Tom Lane | 2004-12-20 18:24:47 | Re: Scheduler in Postgres |