On Thu, Mar 21, 2013 at 5:58 AM, Tom Lane wrote:
> Josh Berkus writes:
> > I just noticed that if I use a tstzrange for convenience, a standard
> > btree index on a timestamp won't get used for it. Example:
>
> > table a (
> > id int,
> > val text,
> > ts timestamptz
> > );
>
Josh Berkus writes:
> I just noticed that if I use a tstzrange for convenience, a standard
> btree index on a timestamp won't get used for it. Example:
> table a (
> id int,
> val text,
> ts timestamptz
> );
> index a_ts on a(ts);
> SELECT * FROM a WHERE ts <@ tstzrange('2013-
On 21/03/13 13:44, David Rees wrote:
On Thu, Mar 14, 2013 at 4:37 PM, David Boreham wrote:
You might want to evaluate the performance you can achieve with a single-SSD
(use several for capacity by all means) before considering a RAID card + SSD
solution.
Again I bet it depends on the applicatio
On Wed, Mar 20, 2013 at 6:44 PM, David Rees wrote:
> On Thu, Mar 14, 2013 at 4:37 PM, David Boreham wrote:
>> You might want to evaluate the performance you can achieve with a single-SSD
>> (use several for capacity by all means) before considering a RAID card + SSD
>> solution.
>> Again I bet it
On 3/20/2013 7:44 PM, David Rees wrote:
> On Thu, Mar 14, 2013 at 4:37 PM, David Boreham wrote:
>> You might want to evaluate the performance you can achieve with a single-SSD
>> (use several for capacity by all means) before considering a RAID card + SSD
>> solution.
>> Again I bet it depends on
On 3/20/2013 6:44 PM, David Rees wrote:
On Thu, Mar 14, 2013 at 4:37 PM, David Boreham wrote:
You might want to evaluate the performance you can achieve with a single-SSD
(use several for capacity by all means) before considering a RAID card + SSD
solution.
Again I bet it depends on the applica
On Thu, Mar 14, 2013 at 4:37 PM, David Boreham wrote:
> You might want to evaluate the performance you can achieve with a single-SSD
> (use several for capacity by all means) before considering a RAID card + SSD
> solution.
> Again I bet it depends on the application but our experience with the ol
Folks,
I just noticed that if I use a tstzrange for convenience, a standard
btree index on a timestamp won't get used for it. Example:
table a (
id int,
val text,
ts timestamptz
);
index a_ts on a(ts);
SELECT * FROM a WHERE ts <@ tstzrange('2013-01-01','2013-01-01 00:10:
