Re: efficient data reduction (and deduping)
От
Kevin Grittner
Тема
Re: efficient data reduction (and deduping)
Дата
Msg-id
4F4F70DE0200002500045D73@gw.wicourts.gov
Ответ на
efficient data reduction (and deduping) (Alessandro Gagliardi)
Список
Дерево обсуждения
efficient data reduction (and deduping) Alessandro Gagliardi <alessandro@path.com>
Re: efficient data reduction (and deduping) "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: efficient data reduction (and deduping) Alessandro Gagliardi <alessandro@path.com>
Re: efficient data reduction (and deduping) "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: efficient data reduction (and deduping) Peter van Hardenberg <pvh@pvh.ca>
Re: efficient data reduction (and deduping) Alessandro Gagliardi <alessandro@path.com>
Re: efficient data reduction (and deduping) Craig James <cjames@emolecules.com>
Re: efficient data reduction (and deduping) Alessandro Gagliardi <alessandro@path.com>
Re: efficient data reduction (and deduping) Claudio Freire <klaussfreire@gmail.com>
Re: efficient data reduction (and deduping) Alessandro Gagliardi <alessandro@path.com>
Re: efficient data reduction (and deduping) Claudio Freire <klaussfreire@gmail.com>
Re: efficient data reduction (and deduping) Alessandro Gagliardi <alessandro@path.com>
Re: efficient data reduction (and deduping) Claudio Freire <klaussfreire@gmail.com>
Alessandro Gagliardi wrote: > hr_timestamp timestamp without time zone, In addition to the responses which more directly answer your question, I feel I should point out that this will not represent a single moment in time. At the end of Daylight Saving Time, the value will jump backward and you will run through a range of time which will overlap existing entries. There is almost never a good reason to use TIMESTAMP WITHOUT TIME ZONE -- TIMESTAMP WITH TIME ZONE is required if you want the value to represent a moment in time. -Kevin
В списке pgsql-performance по дате отправления