On Tue, Feb 7, 2012 at 3:11 PM, Igor Neyman wrote:
> From: Gudmundur Johannesson [mailto:gudmundur.johannes...@gmail.com]
> Sent: Thursday, February 02, 2012 11:42 AM
> To: Merlin Moncure
> Cc: pgsql-performance@postgresql.org
> Subject: Re: Index with all necessary columns - Postgres vs MSSQL
>
On Tue, Feb 7, 2012 at 11:59 AM, Gudmundur Johannesson
wrote:
> On Tue, Feb 7, 2012 at 3:11 PM, Igor Neyman wrote:
>>
>> From: Gudmundur Johannesson [mailto:gudmundur.johannes...@gmail.com]
>> Sent: Thursday, February 02, 2012 11:42 AM
>> To: Merlin Moncure
>> Cc: pgsql-performance@postgresql.org
From: Gudmundur Johannesson [mailto:gudmundur.johannes...@gmail.com]
Sent: Thursday, February 02, 2012 11:42 AM
To: Merlin Moncure
Cc: pgsql-performance@postgresql.org
Subject: Re: Index with all necessary columns - Postgres vs MSSQL
Hi,
I want to start by thanking you guys for a quick response
May be I should first try to partition the table by date and see if that
helps.
Thanks,
- Gummi
On Thu, Feb 2, 2012 at 8:30 PM, Merlin Moncure wrote:
> On Thu, Feb 2, 2012 at 10:41 AM, Gudmundur Johannesson
> wrote:
> > Do you think I should try using the latest build of the source for 9.2
Hi,
I want to start by thanking you guys for a quick response and I will try to
provide all the information you request.
1) What version am I running:
"PostgreSQL 9.1.2, compiled by Visual C++ build 1500, 64-bit"
2) Schema:
CREATE TABLE test( id integer, dtstamp timestamp without time zone,
rat
Hi,
Here are the answers to your questions:
1) I change the select statement so I am refering to 1 day at a time. In
that case the response time is similar. Basically, the data is not in
cache when I do that and the response time is about 23 seconds.
2) The list of IDs is provided by the middle
On Thu, Feb 2, 2012 at 10:41 AM, Gudmundur Johannesson
wrote:
> Do you think I should try using the latest build of the source for 9.2 since
> index-only-scan is "ready" according to
> http://www.depesz.com/index.php/2011/10/08/waiting-for-9-2-index-only-scans/
> ?
hm, interesting.
You are simpl
On Wed, Feb 1, 2012 at 12:50 PM, Gudmundur Johannesson
wrote:
> Here are the answers to your questions:
> 1) I change the select statement so I am refering to 1 day at a time. In
> that case the response time is similar. Basically, the data is not in cache
> when I do that and the response time
On Wed, Feb 1, 2012 at 10:10 AM, Gudmundur Johannesson
wrote:
> Hi,
>
> I have a table in Postgres like:
> CREATE TABLE test
> (
> id integer,
> dtstamp timestamp without time zone,
> rating real
> )
> CREATE INDEX test_all
> ON test
> USING btree
> (id , dtstamp , rating);
>
> My db h
On Wed, Feb 1, 2012 at 11:10 AM, Gudmundur Johannesson
wrote:
> Hi,
>
> I have a table in Postgres like:
> CREATE TABLE test
> (
> id integer,
> dtstamp timestamp without time zone,
> rating real
> )
> CREATE INDEX test_all
> ON test
> USING btree
> (id , dtstamp , rating);
>
> My db h
Hi,
I have a table in Postgres like:
CREATE TABLE test
(
id integer,
dtstamp timestamp without time zone,
rating real
)
CREATE INDEX test_all
ON test
USING btree
(id , dtstamp , rating);
My db has around 200M rows and I have reduced my test select statement down
to:
SELECT count(1) FR
11 matches
Mail list logo
