Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: date_part()/EXTRACT(second) behaviour with time data type
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Greg Stark <stark(at)mit(dot)edu>
- Cc: Postgres <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: date_part()/EXTRACT(second) behaviour with time data type
- Date: Wed, 29 Jul 2009 15:00:58 -0400
- Message-id: <28560.1248894058@sss.pgh.pa.us> <text/plain>
Greg Stark <stark(at)mit(dot)edu> writes: > On Wed, Jul 29, 2009 at 5:15 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote: >> I agree that we should change it, but should we back-patch it, and if so >> how far? > Well at least to 8.4 so someone who has just always been using > downloaded binaries or binaries compiled with the default > configuration continues to get the same behaviour. > My inclination would be to backpatch it further back. But I'm not 100% > sure either. Given the lack of prior complaints, I'm thinking just to 8.4 is a good compromise. Any objections out there? regards, tom lane
- References:
- date_part()/EXTRACT(second) behaviour with time data type
- From: Gregory Stark
- Re: date_part()/EXTRACT(second) behaviour with time data type
- From: Tom Lane
- Re: date_part()/EXTRACT(second) behaviour with time data type
- From: Greg Stark
- date_part()/EXTRACT(second) behaviour with time data type
- Prev by Date: Re: xpath not a good replacement for xpath_string
- Next by Date: Re: xpath not a good replacement for xpath_string
- Previous by thread: Re: date_part()/EXTRACT(second) behaviour with time data type
- Next by thread: 8.4 win32 shared memory patch
- Indexes: