| From: | David Salisbury <salisbury(at)globe(dot)gov> | 
|---|---|
| To: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Fwd: Re: Dynamic update of a date field | 
| Date: | 2012-02-16 22:34:21 | 
| Message-ID: | 4F3D846D.3010803@globe.gov | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
On 2/16/12 7:27 AM, Andreas Kretschmer wrote:
> Musial, Jan (GIUB)<jan(dot)musial(at)giub(dot)unibe(dot)ch>  wrote:
>> smallint,month smallint,day smallint,time_stamp date); I would like to
>
> That's silly, use one (and only one) field, timestamp (or timestamptz)
> Don't use never ever multiple columns for the same information!
Would it not be advantageous to replicate information in the above
form if you wanted to, say, get all records in the month of May, and
therefore create an index on the month field?  I would think that
would be more efficient than creating a functional index on a timestamp.
And if you're not too picky, that would give an index that couldn't
be done on a timestamptz field, as that's mutable.
-ds
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2012-02-16 22:45:18 | Re: Fwd: Re: Dynamic update of a date field | 
| Previous Message | Guillaume Lelarge | 2012-02-16 22:17:33 | Re: running multiple versions |