From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Mark Stosberg <mark(at)summersault(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_autovacuum should allow NULL values |
Date: | 2007-02-23 21:14:44 |
Message-ID: | 20070223211444.GA6210@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Mark Stosberg wrote:
> Jim C. Nasby wrote:
> > On Fri, Feb 23, 2007 at 04:08:45PM -0300, Alvaro Herrera wrote:
> >> Mark Stosberg wrote:
> >>> I just tried to add something to the pg_autovacuum table for the first
> >>> time today (with 8.1). I wanted to make the simplest possible entry:
> >>> Disable auto-vacuuming for a table. However, the data model requires
> >>> that I also enter values for:
> >>>
> >>> vac_base_thresh
> >> You can use any negative value on these settings (-1 works fine, for
> >> example).
> >
> > We should really make that the default so that you don't have to worry
> > about other fields...
>
> A default would be helpful, but I think "NULL" is a lot more intuitive
> as a placeholder "don't know/ don't care", than "-1" is.
>
> Adding a default of -1 seems like a more cumbersome way to express the
> same thing to me.
To be frank, I don't remember what the rationale was for not using
NULLs. Simplicity of code, I guess.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-02-23 21:24:16 | 5 Weeks till feature freeze or (do you know where your patch is?) |
Previous Message | Ed L. | 2007-02-23 21:02:34 | db stats vs table stats |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-02-23 21:24:16 | 5 Weeks till feature freeze or (do you know where your patch is?) |
Previous Message | Mark Stosberg | 2007-02-23 20:59:33 | Re: pg_autovacuum should allow NULL values |